The short answer
Nebim Shopify integration is the automatic transfer of product cards, size-and-colour stock and prices from Nebim V3 to your Shopify store, and of orders, customers and payments from Shopify back into Nebim V3. The connection is built through a middleware layer between the Nebim V3 Integrator REST API services and the Shopify GraphQL Admin API and webhooks.
The integration is usually delivered either with a product from a Nebim partner integrator or with custom-built middleware. A single-channel fashion brand typically goes live in 8–12 weeks; omnichannel projects that also sell store inventory online take 12–18 weeks.
This guide draws on the field experience of Byte Digital, a Shopify Plus Partner that has served Shopify brands for 7 years.
Which data is synchronised between Nebim and Shopify?
Products, stock and prices flow from Nebim to Shopify; orders, customers and payments flow from Shopify to Nebim. Product content (descriptions, images, SEO copy) is mostly managed in Shopify.
Data | Direction | Frequency | Nebim V3 side | Shopify side |
|---|---|---|---|---|
Product card | Nebim → Shopify | On change | Item code, product hierarchy, attributes | Product, metafields, collection rules |
Colour and size | Nebim → Shopify | On change | Colour code and size dimension (item dimensions) | Option and ProductVariant |
Barcode | Nebim → Shopify | On change | Variant barcode | Variant barcode and SKU |
Stock | Nebim → Shopify | Every 5–15 minutes or event-driven | Available stock per warehouse and store | InventoryLevel, Location |
Price | Nebim → Shopify | On change | Price lists, discounted prices | Price, compare-at price |
Order | Shopify → Nebim | Real time (webhook) | Retail or wholesale sales order | Order |
Customer | Shopify → Nebim | With the order | Retail customer / current account | Customer |
Payment | Shopify → Nebim | With the order | Payment type, credit card, instalments | Transaction |
Shipment | Nebim → Shopify | On dispatch | Dispatch note, tracking number | Fulfillment |
Return | Two-way | Event-driven | Return invoice / dispatch note | Return, Refund |
Nebim V3 integration interfaces and product structure
The recommended way to connect to Nebim V3 from outside is the REST API services of Nebim V3 Integrator; according to Nebim, these services enable real-time integration and stay backward-compatible across V3 version changes (Nebim).
Interface | Used for | Note |
|---|---|---|
Nebim V3 Integrator (REST API) | Writing orders, customers and payments; reading products, stock and prices | Recommended; writes pass through Nebim's business rules |
SQL Server database (read-only) | Bulk reading of products and stock, reporting | Writing directly to tables is unsupported and risky; use for reads only |
Off-the-shelf integrator products | Standard product, stock and order flows | Shopify support and local fields vary by integrator |
Older installations running Nebim Winner can also be integrated, but new projects should target V3.
The size-colour matrix is the most critical mapping. In Nebim a product is held under one code with colour and size dimensions; in Shopify every colour-size combination is a variant. Two decisions must be made up front:
Each colour as its own product, or as variants of one product? For fashion brands, creating a separate Shopify product per colour and linking "colour siblings" with a metafield gives better visibility on collection pages and better SEO.
Variant limit: For products with many colours and a wide size range, keep Shopify's per-product variant limit in mind.
Nebim Shopify integration methods
An off-the-shelf integrator suits standard single-channel selling; custom middleware is the better choice for brands with store inventory, marketplaces or bespoke business rules.
Method | When to choose it | Setup time | Flexibility | Ongoing cost |
|---|---|---|---|---|
Off-the-shelf Nebim integrator | Single warehouse, standard order flow | 3–6 weeks | Low–medium | Monthly licence |
Multichannel integration platform | When marketplaces such as Trendyol or Hepsiburada are also connected to Nebim | 4–8 weeks | Medium | Monthly licence, possibly per-order fees |
Custom-built middleware | Omnichannel, colour-based product structure, bespoke campaign and return rules | 8–18 weeks | Highest | Hosting + maintenance |
Whichever method you choose, the architecture is the same: Shopify sends the order to the middleware via webhook and the middleware writes it to Nebim V3 Integrator; stock and price changes are read from Nebim and pushed to Shopify via the GraphQL Admin API, using Bulk Operations for large catalogues. The middleware should include an order queue, automatic retries and an error dashboard.
Omnichannel, e-invoicing and returns for fashion brands with stores
Most brands on Nebim have physical stores; the real value of the integration is making store inventory sellable online.
Sellable stock rule: Nebim defines which warehouses' and stores' stock is opened to online sales. The last 1–2 units in a store are usually held back; this safety-stock rule is managed in the middleware.
Shopify locations: The e-commerce warehouse and every store opened for online sales are set up as separate Shopify locations, so "buy online, pick up in store" and "ship from store" run on Shopify's built-in order routing.
e-Invoice and e-Archive: Invoices are issued from Nebim V3 through the e-transformation provider Nebim works with. Corporate invoice details from Shopify (company name, tax office, tax number) must be passed across in full.
Returns to store: Returning an online purchase to a store is the most complex flow in fashion retail. Decide at the start whether the return is initiated from the store POS in Nebim or from the middleware, and how it is matched to the return in Shopify.
Campaigns and discounts: Discount codes and automatic discounts in Shopify must be passed to Nebim line by line with the order; otherwise revenue and margin reports will not reconcile.
Nebim Shopify integration step by step: timeline and cost
A single-channel fashion brand goes live in 8–12 weeks; an omnichannel brand that sells store inventory online takes 12–18 weeks.
Discovery (1–2 weeks): Sellable warehouses, price lists, campaign and return processes are mapped with Nebim users.
Product model and mapping (1–2 weeks): Size-colour structure, translating the product hierarchy into Shopify collections, mapping payment types and store codes.
Development (3–8 weeks): Products and stock first, then orders and payments, finally returns and invoicing.
Testing (2–3 weeks): End-to-end scenarios in a Nebim test company; reconciliation with accounting and store operations.
Initial load and go-live (1–2 weeks): Catalogue and images are loaded in bulk; go-live is scheduled outside season launches and campaign periods.
Hypercare (2–4 weeks): Sync errors are tracked in a daily report.
The main cost drivers are the number of stores and warehouses opened for sale, the number of products and breadth of sizes and colours, whether marketplace integrations are part of the same project, omnichannel flows such as returns to store, and whether custom fields or reports are needed on the Nebim side.
The 6 most common mistakes in Nebim Shopify integration
Most problems stem from not settling the product model and store stock rules up front.
Writing directly to the Nebim database: Orders and customers should be written through Nebim V3 Integrator, not into SQL tables; otherwise the integration breaks on version upgrades.
Changing the size-colour structure later: Switching to a "one product per colour" model after launch breaks URLs and SEO.
Opening store stock without a safety margin: Items that are not on the shelf or are damaged get sold, and cancellation rates rise.
Not using the barcode as the matching key: Matching by product name or Shopify ID creates duplicate products during catalogue updates.
Not passing discounts line by line: Revenue, campaign performance and refund amounts appear wrong in Nebim.
Ignoring conflicts with marketplace integrations: If the same stock is sent to Shopify and Trendyol through separate integrations, stock deduction must be managed from a single source for both.
Nebim Shopify integration with Byte Digital
Byte Digital is an Istanbul-based Shopify Plus Partner that has provided Shopify migration, theme development and ERP integration services to leading Turkish brands for 7 years. Having worked with brands such as Altınyıldız and Züber, our team maps your Nebim product and store structure correctly onto Shopify's variants, locations and order routing.
Share your Nebim version, number of stores and monthly order volume, and we will prepare a free pre-assessment with the right method, timeline and an estimated budget.
Request a free Nebim Shopify pre-assessment →
Frequently asked questions
Can Nebim be integrated with Shopify?
Yes. Nebim V3 can be integrated with Shopify through the Integrator REST API services. Products, size-colour stock and prices flow automatically from Nebim to Shopify; orders, customers and payments flow from Shopify to Nebim.
How long does a Nebim Shopify integration take?
For a standard fashion brand with one warehouse, 8–12 weeks. Omnichannel projects that open store inventory for sale or include ship-from-store or returns to store take 12–18 weeks.
Can store inventory in Nebim be sold on Shopify?
Yes. Each store is set up as a separate location in Shopify and its Nebim stock is synced to that location. A safety-stock rule can hold back the last few units in each store from online sales.
How are colours and sizes in Nebim transferred to Shopify?
Nebim's colour and size dimensions become variant options in Shopify. For fashion brands, creating each colour as a separate product and linking the colours together usually gives better collection visibility and SEO.
Can Nebim Winner be integrated with Shopify?
It can, but the interface options are more limited than V3. We recommend brands planning a Shopify move build the integration on Nebim V3.
Does the Nebim integration change when moving from Ticimax or ikas to Shopify?
The Nebim side stays largely the same; what changes is the connection on the Shopify side. Redirects for product URLs and customer data migration should be planned alongside the integration.
Sources
Nebim — Integration with external systems
Nebim — e-Dispatch
