What does a Zid store developer actually work on?
A Zid store developer works on the three layers that sit outside Zid's own settings: the storefront theme, apps that use the Zid API, and connections between Zid and your other systems. Settings, product entry and installing apps are merchant tasks; you do not need a developer for those.
The work usually starts with a specific pain. Stock in the warehouse system and stock in Zid disagree. The accountant retypes every order. The product page cannot show the size guide your customers keep asking about. A B2B customer needs prices nobody else sees. Each of these is a small, well-defined project, and none of them needs a full rebuild.
Occasionally the pain is bigger: the store has outgrown the platform. Part of a good Zid store developer's job is saying so early rather than stacking workarounds. We cover that decision later on this page.
- Storefront: Vitrin themes, sections, settings schemas and locale files.
- Apps: private apps for one store, or public apps listed in the App Market.
- Integrations: ERP, accounting, shipping, WhatsApp, spreadsheets, dashboards.
- Moves: onto Zid from another platform, or off Zid when it no longer fits.
Before hiring a Zid developer: what to try first
Check three things before paying for code: your plan's built-in features, the Zid App Market, and whether the requirement is really a process problem. Half the requests we hear can be solved by one of those, and we will tell you if yours can.
Zid adds features over time, and the App Market covers many common needs such as reviews, loyalty, shipping carriers and marketing tools. If an app does most of what you need, a monthly fee is cheaper than a custom build and someone else maintains it.
A process problem looks like a software problem but is not. If orders go wrong because two staff members both edit stock, an integration will not fix it; a clear rule about who owns stock will. We ask about the process before quoting code.
You probably do not need a developer if
The need is common to most stores, an App Market app covers it, and you can accept that app's layout and wording.
You do need a developer if
Data must flow automatically between Zid and a system you already run, the storefront needs a layout no theme setting allows, or a workflow is specific to your business.
Public vs private Zid apps: which one does your store need?
A private Zid app is installed on your store only; a public app is listed in the Zid App Market for any merchant to install. For a single store's custom workflow, a private app is almost always the right choice: no public review queue, no support duties to other merchants, and code shaped to your business alone.
Zid's developer documentation states that private apps require the merchant to be on the Professional or Enterprise plan, or to have API access activated from the dashboard. So check your plan before commissioning one. It also states that shipping and logistics apps cannot be private; they must be public.
A public app makes sense when you are building a product to sell to many Zid merchants, or when you are a carrier or service provider who wants every store to connect. That path adds a partnership agreement, Zid's review before publication, pricing and trial settings, and ongoing support for stores you have never met.
- Private: one store, faster to ship, needs Professional or Enterprise plan or API access.
- Public: many stores, listed after review, subscription pricing, support obligations.
- Shipping and logistics apps: public only, per Zid's documentation.
- Embedded apps: either type can appear inside the Zid merchant dashboard in an iframe.
Source for plan and app-type rules: Zid developer documentation. Zid can change these rules, so we recheck them at quote time.
How a Zid app connects to your store: OAuth, tokens and webhooks
A Zid app connects through OAuth 2.0: you approve the app in your dashboard, Zid issues tokens, and the app's server uses them to call the Zid API on your store's behalf. You never share your owner password with a developer, and you can revoke the app at any time.
Zid's documentation describes two headers on every API call, an Authorization token for the app and an X-Manager-Token for the specific store, and says both tokens expire after one year, with refresh advised at around ten months. That detail matters: an integration that silently stops a year after launch is a classic Zid failure. We build token refresh and an alert into every app.
Webhooks are how the app hears about changes. Zid sends events for orders, products, product categories, customers and abandoned carts, so the app can react within seconds instead of polling. Zid also documents webhook health tracking and recovery of broken webhooks, which we wire into monitoring.
Why the app must run on a server
Zid's documentation is explicit that apps run server-side so the client secret and tokens are never exposed in the browser. Hosting sits in your cloud account, not ours.
Rate limits
Zid documents a limit of 60 API requests per minute per application per store. Bulk jobs such as a full stock sync are queued and paced to respect it.
Syncing Zid with an ERP or accounting system
A reliable Zid ERP sync decides one owner for each kind of data, moves changes by webhook, and runs a nightly check that catches anything the webhooks missed. Most failed integrations skip the owner rule, and two systems end up overwriting each other.
Typically Zid owns orders and customers, and the ERP owns products, prices and stock. A paid order in Zid creates a sales order or invoice in the ERP. A stock change in the warehouse updates Zid. Refunds and cancellations flow the same way as orders, with a reason code so the accountant can reconcile them.
Accounting links follow the same pattern with less data: paid orders, refunds and payment fees posted as entries, grouped by day if the accountant prefers. Where the business issues e-invoices, the sync has to hand the right data to its e-invoicing solution; our ZATCA e-invoicing integration page covers that side.
- Decide the owner: which system is the truth for products, prices, stock, orders and customers.
- Map fields: SKUs, variants, tax categories, payment methods and order statuses.
- Move changes by webhook, with retries and a dead-letter log for failures.
- Reconcile nightly: counts and totals compared, differences reported on WhatsApp or email.
- Pace bulk jobs to Zid's rate limit and your ERP's own limits.
What can a Zid theme developer change, and where are the limits?
On Zid you can change almost everything a shopper sees before checkout, inside a fixed frame. Zid themes run on the Vitrin engine with Jinja templates, and per Zid's theme documentation every template extends a base layout that must include Vitrin's required head and body tags.
Inside that frame a Zid theme developer can restyle page templates, add new sections with settings your team edits from the dashboard, add locale strings for Arabic and English, and show data such as size guides or delivery estimates. Settings follow a JSON Schema, and themes are validated before upload.
The checkout itself is not part of the theme layer, and error rendering is handled by Zid's SDK. If a request involves changing how checkout works, the realistic answers are a Zid setting, an App Market app, a private app that adds logic around the order, or a platform move. We tell you which before quoting.
Legacy Twig themes
Zid's migration guide says legacy Twig themes were set to be deprecated by 28 December 2025, with only Vitrin themes remaining supported in the Theme Market. If your store still runs heavy Twig customisations, plan a Vitrin rebuild rather than more patches.
Customise or build fresh
Customising a Theme Market theme is cheaper and keeps its updates. A fresh Vitrin theme suits brands with a strict design system or unusual product pages, and costs more to maintain.
Zid shipping app integrations: what is built in and what needs code
Carrier connections on Zid come from shipping apps in the App Market, and per Zid's documentation those apps are always public. So a developer rarely writes the carrier connection itself; the work is configuring it well and building what surrounds it.
Common gaps sit before and after the label. Before: splitting orders between two warehouses, picking lists sorted the way your staff walk the shelves, or holding cash-on-delivery orders until the customer confirms on WhatsApp. After: pushing tracking updates to customers in Arabic, flagging parcels stuck with the courier, and handling returns so stock goes back to the right place.
The national address matters here. Saudi couriers work best with complete address data, and a checkout that collects it cleanly saves failed deliveries later. If you run your own riders rather than a courier, that is a different build; see delivery app development.
- Install and test the carrier apps you have contracts with.
- Map Zid order statuses to carrier statuses so customers see one clear state.
- Automate customer updates for dispatched, out for delivery and failed attempts.
- Report exceptions daily instead of discovering them from complaints.
How much does a Zid store developer cost?
With us, Zid integrations start from US$600, theme and store work starts from US$750, and private apps with admin screens start from US$900. Other Zid developers' quotes vary widely; the price difference comes from scope and quality of error handling more than from rates.
A one-way push of paid orders into accounting is a small job. A two-way ERP sync with stock, prices, refunds and nightly reconciliation is several times larger, because every edge case needs a rule. On the theme side, adding two sections is small; rebuilding a legacy Twig theme on Vitrin is a proper project.
- Number of Zid events handled and whether data flows one way or both ways.
- Quality of the other system's API: documented REST is quick, spreadsheets and exports are slower.
- Data clean-up: mismatched SKUs and duplicate customers must be fixed before any sync.
- Theme scope: sections added, templates changed, or a full Vitrin rebuild.
- Admin screens: a private app with its own settings pages costs more than a background job.
Every Zid store developer quote from us is itemised, so you can drop lines you do not need. Nothing is billed before you approve it in writing.
How long does Zid development take?
Integrations usually take 2–4 weeks, theme projects and store builds 4–8 weeks, and private apps with admin screens 6–12 weeks. The slowest part is rarely code; it is getting access to the other system and agreeing field mappings.
We shorten that by asking for access and sample data in the first days. A test copy of your ERP, a sample export of fifty orders, and a staff account on Zid with the right permissions let us build against real data from week one.
- Week 1: access, sample data, field mapping and owner rules agreed.
- Weeks 2–3: webhook handlers, sync jobs or theme sections built on staging.
- Week 3–4: testing with real orders, reconciliation report, staff walkthrough.
- Longer projects: admin screens, public app review, or a Vitrin rebuild add phases.
When should a Zid store move to Shopify, WooCommerce or a custom build?
Move off Zid when the workarounds cost more each month than a migration would, not because of one missing feature. Zid serves many Saudi stores well; leaving is a big job, and it should solve a problem you can name.
Signals worth taking seriously: you need checkout behaviour Zid does not support, your catalogue or B2B pricing rules need a data model Zid cannot hold, you are selling in many countries with different storefronts, or you are building a multi-seller platform. For that last case, see multi vendor marketplace development.
If you do move, run both stores in parallel for a short period, redirect every product and category URL, and keep order history accessible. Customers' saved accounts are the hardest part; plan how they will log in on the new store.
Stay on Zid when
Your needs are mostly integrations and design, you value local payments and shipping out of the box, and you do not want to manage hosting.
Consider Shopify when
You sell internationally with several markets, or need a larger app ecosystem. Our Shopify developer page covers Saudi-specific points.
Consider custom when
Your pricing, checkout or seller model is the business itself. Custom builds start from US$900.
Can a Zid store developer improve SEO and AI-search visibility?
Yes, within the platform's limits. A developer can make theme templates output clean headings, fast images and structured data, and can fix internal links and category content blocks. Zid controls hosting and some URL behaviour, so the work focuses on what the theme and content can change.
The most useful fixes are usually boring: unique titles and descriptions per product in both languages, category pages with a short useful introduction instead of a bare grid, image sizes that do not slow down mobile pages, and no duplicate content between Arabic and English versions.
AI assistants that answer shopping questions quote pages with clear facts: materials, sizes, delivery areas, return terms. Adding those as consistent fields in the theme makes every product page more quotable. Ongoing work fits monthly SEO from US$150/mo; see SEO services in Saudi Arabia. No one can guarantee rankings, and we do not claim to.
Giving a Zid developer access safely
Give a developer a staff account with only the permissions the job needs, and approve apps through OAuth; never share the owner login. Zid has user roles and permissions for exactly this, and we ask for the narrowest role that works.
For integrations, the app's tokens live on a server in your cloud account, and secrets stay out of code repositories. When the project ends, you can remove the staff account in one click and the app keeps running under your ownership. If you ever want to stop using the app, revoking it cuts its access immediately.
Customer data that flows through an integration is personal data under Saudi law. We sync only the fields the other system needs and log access. Our PDPL compliance guide for websites explains the wider obligations your lawyer will look at.
- Staff account with a limited role, not the owner account.
- App tokens on your server, rotated before the one-year expiry.
- Code in a repository you own, with access removed at handover if you wish.
- Only required customer fields synced to other systems.
Hiring a Zid store developer in India from Saudi Arabia: how it works
It works like hiring any remote specialist, with a friendly time difference. India is two and a half hours ahead, so your Sunday-to-Thursday mornings are our late mornings and early afternoons, and we answer WhatsApp every day including Friday and Saturday.
We talk on Google Meet or Zoom, share progress on a staging store or test app, and send a written note after each call. Quotes and invoices are in US dollars from India, paid by Wise or bank wire, and the peg between the riyal and the dollar keeps the cost predictable. There is no Saudi office and no in-person visits.
What we need from you is decisions, access and Arabic copy. We write English and build bilingual interfaces; you or your team supply or approve the Arabic text that appears in the theme or app.
Days 1–5
Call about the problem, staff account and sample data shared, written scope and field map sent back for your approval.
Days 6–10
First working piece on staging, such as paid orders arriving in a test copy of your accounting system, reviewed together on a call.
How to vet a Zid developer before you hire
Ask how they will handle failure, not just success. A developer who can explain retries, token expiry, rate limits and nightly reconciliation has built real Zid integrations; one who only talks about features probably has not.
Ask where the code and tokens will live, and who owns them. The answer should be your accounts. Ask what happens when Zid changes its theme engine or API; the recent move from Twig to Vitrin is a good test question. And ask for an itemised quote, so you can see what you are paying for.
- Can they explain public vs private apps and your plan's eligibility?
- Do they build token refresh and alerting into the app?
- Will they respect Zid's per-store rate limit on bulk jobs?
- Do theme changes use sections and settings rather than hard-coded content?
- Is the code and hosting in your name from day one?
- Do they tell you when an App Market app would be cheaper?
Worked example: a hypothetical Riyadh supplements store on Zid
Imagine a sports-nutrition store in Riyadh on Zid's Professional plan, with a warehouse ERP that holds stock and batch expiry dates. Staff retype every order into the ERP, and twice a month the store sells items it no longer has. This is a made-up scenario to show how a Zid store developer would approach it.
The fix is a private Zid app. Paid-order webhooks create sales orders in the ERP. The ERP pushes stock changes to Zid every few minutes, paced within Zid's rate limit. A nightly job compares order counts and stock levels and sends differences to the manager on WhatsApp. Tokens refresh automatically with an alert if anything fails.
On the storefront, a new Vitrin section shows the batch expiry month on product pages, pulled from a product field the app keeps up to date. The quote would start from US$600 for the sync alone and from US$900 if the owner also wants an admin screen to manage mapping rules. Two months of free maintenance cover the first seasonal rush.
What you receive when the Zid project ends
You receive working code in your repository, the app running in your cloud account, a short runbook, and a recorded walkthrough. The runbook covers where logs are, how to re-run a failed sync, how tokens refresh, and whom to call if Zid changes something.
Two months of free maintenance follow launch. After that, maintenance starts from US$120/mo a month if you want us to keep watching. Theme changes come with notes on which sections and settings were added, so another developer can pick them up without guessing.
- Source code and deployment notes in your repository.
- App hosting and secrets in your cloud account.
- Field mapping document and owner rules for each data type.
- Recorded walkthrough for your staff in English.
- List of Zid settings and apps changed during the project.