ikas Theme Development

ikas Custom Theme Development

Not a pre-built theme with your logo dropped in. A storefront coded from scratch in Next.js and TypeScript, where you decide what your team can change without a developer.

Next.js + TypeScript
Connected ikas partner
Source code handover

How It Works

Quick answer

What is ikas custom theme development?

It is the practice of coding your ikas storefront theme from scratch instead of selecting a pre-built template. A theme developer writes React components that merchants can place on any page, and defines which fields of those components stay editable in the theme editor.

The distinguishing question is not how the store looks on launch day. It is who sets the limit of customisation. In a pre-built theme that limit was decided by someone else, before they knew your brand existed.

See our packages

Tech StackLast updated: September 17, 2026

What an ikas theme is actually built on

This is not trivia. The stack decides who can build your theme, how fast it can run, and how much your team can change without calling a developer.

Next.js, TypeScript and MobX

ikas themes are built on Next.js, TypeScript and MobX. In practice this means a theme is a real front-end application, not a markup template with placeholders sprinkled in. Server rendering, routing and state management come from a modern stack — which is exactly why performance and SEO become decisions you can influence rather than properties you inherit from whoever wrote the template.

You build components, not pages

A theme developer does not hand over finished pages. They write React components — building blocks a merchant can place on whichever page they want from the theme editor. Your homepage is then assembled from those blocks rather than being hard-coded. This is why a well-built custom theme keeps paying off: the campaign layout you need next spring is a rearrangement, not a new project.

Custom data types: the part most teams miss

When the basic data types are not enough to capture what a merchant needs to fill in, the developer defines custom data types. It sounds technical but it is the most commercial decision in the project: it is what lets you manage a size chart, a delivery promise, a product badge or a campaign rule as structured data, instead of pasting it into a description field where it can never be filtered, sorted or reused.

Development happens on a development store

Theme work runs against a separate development store connected to a partner account, using the ikas theme development kit. Your live storefront is never the workbench. When source code is uploaded, a theme version is created on the ikas side and the build status can be monitored — which is what makes a planned, reversible release possible in the first place.

Quick answer

What is the difference between a pre-built ikas theme and custom theme development?

In a pre-built theme, merchants can customise only as much as the theme developer allowed them to — the editable fields were decided in advance, for a generic store. In custom theme development, you decide where that boundary sits. Everything else — cost, timeline, visual identity — follows from that single difference.

Custom theme development vs. a pre-built theme on ikas
Feature	Custom theme development	Pre-built theme
Who sets the customisation limit?	You. Components and editable fields are defined around your needs.	The developer who wrote the theme. Only the fields they exposed can change.
Need for a new component	It gets written and added to the theme editor; page structure stays open.	Usually not possible; a similar block is stretched to fit.
Brand-specific fields	Defined as custom data types (size chart, delivery promise, badges).	Limited to the built-in field set; the rest gets squeezed into description text.
Performance	Only the code you use is shipped; a speed budget is set up front.	You carry all the code written to satisfy every possible store.
Upfront cost	Higher — development effort is a real investment.	Low. A reasonable way to start quickly.
Time to launch	Measured in weeks, depending on scope.	Can go live within days.
Long-term cost of change	Falls — the structure is known, so changes are predictable.	Rises — every request becomes a negotiation with the theme's limits.
Visual similarity to competitors	None. The interface exists only in your store.	A family resemblance to every store on the same theme.
Access to source code	Code and documentation are handed over at delivery.	Held by the theme vendor and usually closed.

A pre-built theme is not a mistake — for a brand validating its first catalogue it is often the right call. If you only need design and conversion work on the theme you already run, see ikas web design.

Scope

What custom theme development includes

Six capabilities define the work. Below them, the full deliverable list we agree on before a line of code is written.

Components From Scratch

Instead of trimming a pre-built theme, we write the components your storefront actually needs — each delivered as a building block that is configurable in the theme editor.

Custom Data Types

When the basic data types are not enough, we define custom data types so your team can fill in exactly the fields your catalogue needs.

Performance Budget

The theme is built against a measurable speed budget. Unused code, oversized images and render-blocking scripts never enter the codebase in the first place.

Mobile-First

Components are designed at the narrow breakpoint first: tap targets, sticky cart and one-handed reach are planned from the start, not retrofitted.

Integration-Ready

For stores running marketplace, ERP, shipping, payment and marketing tooling, the theme layer is designed not to break those flows.

Versioning & Rollback

Uploading source code creates a theme version on the ikas side. Every release ships with a rollback plan — your store never sits live on an experimental build.

Deliverables

Discovery and scoping workshop; technical audit of the current storefront

Information architecture: page types, component inventory, editable fields

Brand-specific interface design (home, category, product, cart, pre-checkout)

Component development in Next.js and TypeScript

Definition of custom data types and the fields exposed in the editor

Theme settings setup including global colours, typography and favicon

Multi-language groundwork through component translations

Mobile-first responsive behaviour and tap-target review

Accessibility pass: keyboard navigation, focus visibility, contrast

Technical SEO: heading hierarchy, structured data, canonical and hreflang

Performance budget and Core Web Vitals measurement

End-to-end testing on a development store across a browser matrix

Versioning, release plan and rollback scenario

Team training: who changes which field in the theme editor, and how

Handover documentation and source code transfer

Post-launch support and one improvement round

Not sure whether you need a custom theme?

Send us your store URL. We will tell you honestly whether a design round on your current theme would solve it for less.

Call Now

Process

How the project actually runs

Six stages, in order. The first one decides the other five — which is why we do not shorten it.

1. Discovery and scope

Catalogue size, variant structure, campaign rules, integrations and your team's daily workflow all go on the table. The output is not a quote but a component inventory: which page types exist, which blocks live on each, and which fields of those blocks your team will be able to change. No code is written before that list is settled — in custom theme development the real decision is where the editable boundary sits.

2. Interface design

Design sits on top of the component inventory. Every block is designed in both its full and empty state, at both wide and narrow breakpoints. Real-world edge cases — an empty category, a single-image product, a very long product name, a price with no discount — are solved during design rather than discovered after launch.

3. Component development

ikas themes are built on Next.js, TypeScript and MobX; the theme developer writes React components that merchants can place on any page from the theme editor. Development runs against a development store using the ikas theme development kit. This is where configurable props and, where needed, custom data types are defined.

4. Theme editor setup

Code alone is not the deliverable. Global colours, default font, favicon and component translations are configured, and every component's settings panel is labelled in language a non-technical team member understands. The goal is simple: you should not have to come back to us for routine changes.

5. Testing, release and rollback

End-to-end testing happens on the development store: product flow, cart, search, filtering, multi-language behaviour, mobile performance. Uploading source code creates a theme version on the ikas side and the build status is monitored. Nothing goes live until the rollback scenario is written down.

6. Handover and training

Delivery includes source code, component documentation and a short team training session. Which field changes what, and which changes require a developer, is left in writing. Your ability to work independently is the completion criterion.

Performance & SEO

A theme is also a speed decision

Most stores do not lose mobile revenue to design. They lose it to what the theme loads before the first product becomes visible.

Core Web Vitals

LCP, INP and CLS are tracked as delivery criteria, not as a post-launch surprise.

Speed budget

A weight limit is agreed up front; code that breaks it does not get merged.

Technical SEO

Heading hierarchy, structured data, canonical and hreflang are built into components.

No migration loss

URL structure and indexed signals are carried over deliberately, not by luck.

Speed does not come from the theme alone: image sizes, third-party scripts and app count all weigh in. Once the theme is live, growing visibility is a separate discipline — see ikas SEO.

Quick answer

Do you need an ikas partner to get a custom theme?

In practice, yes — and the reason is structural, not commercial. Themes developed on ikas are Private by default: they do not appear in a merchant's dashboard at all. For a theme to become available to your store, the partner account that developed it has to be connected to your store and grant access explicitly.

So the question is not whether a freelancer can write good React. It is whether the account holding your theme can legitimately deliver it to your store — and keep shipping updates to it afterwards.

Our ikas partnership

The theme layer in four facts

Next.jsThe framework ikas themes run on

ComponentsReusable blocks, not fixed pages

PrivateDefault visibility of a custom theme

RemoteHow we work across Türkiye and the EU

ikas Web Design

Design and conversion work on your existing theme, without writing one from scratch.

Open

ikas Store Examples

A gallery of live ikas storefronts built by our team.

Open

ikas Partner

The full scope of our ikas partnership: setup, integration and growth.

Open

ikas SEO

Technical SEO that grows search visibility once the theme is live.

Open

FAQ

ikas custom theme questions

The questions we are actually asked in scoping calls, answered the way we answer them there.

What is ikas custom theme development?

ikas custom theme development means your storefront theme is coded from scratch for your brand instead of being picked from a template. The theme developer writes React components that can be placed on pages, and defines which of their fields are editable from the theme editor. The result is a storefront interface that exists only in your store and that your team can manage without writing code.

What technology are ikas themes built with?

ikas themes are built on Next.js, TypeScript and MobX. The developer connects to a development store using the ikas theme development kit and writes React components. A theme project contains a dedicated folder for components, MobX stores for shared state, and an auto-generated configuration file that holds the component declarations.

Why choose custom theme development over a pre-built theme?

With a pre-built theme, the limit of customisation is set by whoever wrote it — only the fields they exposed can change in the editor. With a custom theme, you set that limit. It becomes the right choice when your catalogue structure is non-standard, your campaign rules are complex, you do not want to share an interface with competitors, or you need control over your performance budget.

Do I need to work with an ikas partner for a custom theme?

In practice, yes. Themes developed on ikas are Private by default, meaning they do not appear in the store dashboard. For a theme to be made available to your store, the partner account that developed it must be connected to your store and explicitly grant access. That is why custom theme work runs through a team with a partner account.

Will my live store go down during development?

No. Development runs on a separate development store, not on your live storefront. Your live store keeps running on its current theme until the new one is tested and approved. The release moment is planned, and every release has a written rollback scenario.

Will I lose SEO when moving to a custom theme?

Not when it is planned properly. Changing a theme does not by itself change your URL structure; the real risk is failing to carry heading hierarchy, structured data, canonical and hreflang tags into the new theme. That is why technical SEO is part of component development scope, not an add-on after launch.

How long does an ikas custom theme take?

It scales with scope and is measured in weeks. The driver is not page count but component count and how deep the editable fields go on each one. Once the component inventory from the discovery workshop is settled, we share a realistic schedule — an estimate given before that is not dependable.

Do we own the source code?

Yes. Delivery includes the source code, component documentation and team training. The aim is not to create dependency but to leave in writing which field changes what and which changes need a developer.

The ikas theme development kit is in beta — is that a risk?

The documentation marks theme development as beta and notes that changes can still happen. That does not mean custom themes are off the table; it is a fact to be managed. In practice it means version tracking, a rollback plan and monitoring documentation changes are part of the project. That is why every release is built to be reversible.

Can the theme be multi-language and multi-currency?

Yes. Component translations can be defined in the theme editor, so interface copy is managed per language. In a multi-language store the real work is less about translation and more about structural decisions: where the language switcher sits, how currency is displayed, and how shipping and return terms change per market. We plan those during the component inventory stage.

Last updated: September 17, 2026

ikas Theme Development

Let's scope your theme properly

Send your store URL and what you cannot do on your current theme. We will come back with a component inventory and a realistic timeline — not a template quote.

Call Now

See live examples

Yükleniyor...

What is ikas custom theme development?

See our packages

What is the difference between a pre-built ikas theme and custom theme development?

Custom theme development vs. a pre-built theme on ikas

Who sets the customisation limit?

You. Components and editable fields are defined around your needs.

The developer who wrote the theme. Only the fields they exposed can change.

Need for a new component

It gets written and added to the theme editor; page structure stays open.

Usually not possible; a similar block is stretched to fit.

Brand-specific fields

Defined as custom data types (size chart, delivery promise, badges).

Limited to the built-in field set; the rest gets squeezed into description text.

Performance

Only the code you use is shipped; a speed budget is set up front.

You carry all the code written to satisfy every possible store.

Upfront cost

Higher — development effort is a real investment.

Low. A reasonable way to start quickly.

Time to launch

Measured in weeks, depending on scope.

Can go live within days.

Long-term cost of change

Falls — the structure is known, so changes are predictable.

Rises — every request becomes a negotiation with the theme's limits.

Visual similarity to competitors

None. The interface exists only in your store.

A family resemblance to every store on the same theme.

Access to source code

Code and documentation are handed over at delivery.

Held by the theme vendor and usually closed.

Process

How the project actually runs

Six stages, in order. The first one decides the other five — which is why we do not shorten it.

ikas Custom Theme Development

What is ikas custom theme development?

What an ikas theme is actually built on

Next.js, TypeScript and MobX

You build components, not pages

Custom data types: the part most teams miss

Development happens on a development store

What is the difference between a pre-built ikas theme and custom theme development?

What custom theme development includes

Components From Scratch

Custom Data Types

Performance Budget

Mobile-First

Integration-Ready

Versioning & Rollback

Deliverables

Not sure whether you need a custom theme?

How the project actually runs

1. Discovery and scope

2. Interface design

3. Component development

4. Theme editor setup

5. Testing, release and rollback

6. Handover and training

A theme is also a speed decision

Core Web Vitals

Speed budget

Technical SEO

No migration loss

Do you need an ikas partner to get a custom theme?

The theme layer in four facts

Before you decide, read these

ikas Web Design

ikas Store Examples

ikas Partner

ikas SEO

ikas custom theme questions

What is ikas custom theme development?

What technology are ikas themes built with?

Why choose custom theme development over a pre-built theme?

Do I need to work with an ikas partner for a custom theme?

Will my live store go down during development?

Will I lose SEO when moving to a custom theme?

How long does an ikas custom theme take?

Do we own the source code?

The ikas theme development kit is in beta — is that a risk?

Can the theme be multi-language and multi-currency?

Let's scope your theme properly

ikas Custom Theme Development

What is ikas custom theme development?

What an ikas theme is actually built on

Next.js, TypeScript and MobX

You build components, not pages

Custom data types: the part most teams miss

Development happens on a development store

What is the difference between a pre-built ikas theme and custom theme development?

What custom theme development includes

Components From Scratch

Custom Data Types

Performance Budget

Mobile-First

Integration-Ready

Versioning & Rollback

Deliverables

Not sure whether you need a custom theme?

How the project actually runs

1. Discovery and scope

2. Interface design

3. Component development

4. Theme editor setup

5. Testing, release and rollback

6. Handover and training

A theme is also a speed decision

Core Web Vitals

Speed budget

Technical SEO

No migration loss

Do you need an ikas partner to get a custom theme?

The theme layer in four facts

Before you decide, read these