Shopify Nebim integration is a system integration that bi-directionally synchronizes product catalog, stock, order, invoice, and customer data between Nebim, Turkey's most widely used retail ERP, and a Shopify store. Nebim is widely used by Turkish businesses operating particularly in the textile, apparel, and omnichannel retail sectors; its integration with Shopify allows these businesses to manage their e-commerce operations through the ERP system. This guide technically covers the integration architecture, how data flows, middleware options, and Turkey-specific e-invoice/e-archive processes.
What is Nebim and Why Integrate it with Shopify?
Nebim, developed by Istanbul-based Nebim Bilgisayar Hizmetleri, is an ERP system widely used in Turkey, especially in the fashion and retail sectors. It consolidates modules for inventory management, purchasing, store management (POS), CRM, e-invoicing, and marketplace integration under a single platform.
The need for Shopify integration typically arises from these scenarios: a business already uses Nebim and is opening a Shopify store; or an existing Shopify store grows to a point where manual data entry becomes unsustainable, leading to an ERP requirement. In both cases, without a data bridge between the two systems, inventory discrepancies, order delays, and accounting errors become inevitable.
Key problems solved by integration:
- If the stock of a product sold on Shopify is not updated in Nebim, the same product might also be sold in a physical store, leading to overselling and return crises.
- Manually entering order information from Shopify into Nebim creates a workload of 2-3 hours per day for 50-100 orders.
- Order data must be transferred to Nebim for e-invoice generation; manual transfer causes delays and increases the risk of errors.
- Those who manage marketplaces like Trendyol and Hepsiburada through Nebim's own integration module also want to include Shopify in this centralized structure.
Technical Architecture of Shopify Nebim Integration
Shopify and Nebim are not directly connected; a middleware (intermediate layer) operates between them. This middleware communicates with the APIs of both systems, transforms data, and manages synchronization.
Basic architectural diagram:
Shopify Admin API (REST/GraphQL)
↕
Middleware / Integration Layer
↕
Nebim API (REST or SOAP)
Key API endpoints used on the Shopify side:
- GET /products.json — fetch product catalog
- POST /inventory_levels/set.json — update inventory
- GET /orders.json — query new orders
- Webhook: orders/create, orders/updated — real-time order notification
Integration on the Nebim side is carried out through Nebim's offered ERP API services. Nebim's API infrastructure can provide services in REST or SOAP format; the current Nebim version and license type determine which endpoints are available. Therefore, before starting the integration, obtain the active API modules and version notes from your Nebim consultant.
Middleware Options: Off-the-shelf vs. Custom Development
As Nodus Works, we have observed that the most frequent problem in Shopify + Nebim projects in Turkey stems from off-the-shelf SaaS middleware's delayed adaptation to Nebim's updated API versions. In major Nebim version updates (e.g., 7.x → 8.x), some endpoint formats change; the integration silently breaks without middleware updates, and the error only becomes apparent when inventory discrepancies are noticed. For this reason, especially for 500+ SKUs and a daily order volume of 100+, we prefer custom middleware development.
Synchronized Data and Flow Directions
Correctly defining which data flows in which direction in Shopify-Nebim integration is critical for both architectural design and debugging.
Critical decision in inventory synchronization: Real-time (webhook-based) or periodic (polling)?
Real-time synchronization, being triggered by webhooks, reflects inventory changes instantly on Shopify. However, webhook support must be available on the Nebim side; if this is not available in older Nebim versions, the middleware regularly querying Nebim (polling) is the only option. A 15-minute polling interval is sufficient for daily order volumes up to 200-300; for higher volumes or during flash sales, there is a risk of inventory discrepancies.
Critical Note: In a multi-location inventory structure (central warehouse + store warehouses), Shopify's inventory location logic must be matched with Nebim's warehouse structure. If only the total stock is transferred without this matching, Shopify will not know which warehouse to ship from, leading to fulfillment errors.
Product Catalog Synchronization: Key Considerations
Product transfer from Nebim to Shopify is the most complex and most frequently error-generating step. Nebim's product data model and Shopify's product model do not perfectly correspond to each other.
Variant matching: In Nebim, size and color combinations are kept as separate SKUs. In Shopify, however, they are listed as variants under a single product. The middleware must convert Nebim's separate SKUs into Shopify's product_id + variant_id structure. A mapping table that correctly matches size/color combinations is essential for this conversion.
Images: Nebim stores product images as file path references; Shopify, however, requires the image's CDN URL. For image transfer, either the image files from Nebim are uploaded to Shopify's Files API, or a URL reference from an external CDN is used.
Product descriptions and SEO fields: Nebim's product description fields are typically logistics-focused (e.g., material code, supplier code). For Shopify's SEO description and meta title, either additional fields are added to Nebim, or manual enrichment is performed on the Shopify side. Our preferred approach at Nodus Works is: let the core product data come from Nebim, let SEO optimization be done in Shopify Admin, and ensure these fields are not overwritten by the integration.
Tip: Before starting the integration, check the product data quality in Nebim. Missing barcodes, inconsistent category codes, or empty product descriptions will be carried over to the integration and cause the same problems in Shopify. Data cleansing is part of the integration setup, not an afterthought.
E-Invoice and E-Archive Integration
In Turkey, the GIB's e-invoice and e-archive mandates make the Shopify-Nebim integration compulsory not only operationally but also legally. Nebim can issue e-invoices through a GIB-approved e-invoice integrator; this process can be triggered when an order from Shopify is transferred to Nebim.
How the process works:
- Payment completed in Shopify → webhook triggered
- Middleware converts order data to Nebim format: customer name, tax ID (for B2B orders), product list, price, VAT
- Nebim records the order in the system
- Nebim's e-invoice module connects to the GIB-approved e-invoice integrator to issue the invoice
- The e-invoice PDF and UBL-TR XML are automatically sent to the customer
Critical additional step for B2B customers: A special field collecting the tax identification number (VKN) is mandatory in the Shopify checkout. This field is not available in Shopify's standard checkout; it is added via Checkout Extensibility (Plus) or a custom application. At Nodus Works, we have observed that approximately 60% of Shopify stores receiving B2B orders neglect to add this field to their checkout, and instead contact the customer separately for the VKN with each order. This both degrades the customer experience and delays invoicing.
Marketplace Integration: Omnichannel Management via Nebim
Nebim's marketplace integration module can directly connect with platforms like Trendyol, Hepsiburada, n11, and Amazon. In this setup, Shopify is also added as a sales channel connected to Nebim, and inventory, order, and invoice management for all channels are handled from a single hub.
Advantage of the omnichannel structure: When stock decreases due to a Trendyol order, this change is reflected in Nebim, and the Shopify stock is also updated via Nebim. This eliminates stock conflicts between channels.
Note: Those who set up marketplace integration via Shopify instead of Nebim (e.g., using Shopify's Trendyol integration apps) encounter a dual-source problem. If Shopify and Nebim simultaneously try to pull Trendyol orders independently, stock and order data will conflict. Therefore, a clear architectural decision must be made: Is Nebim the master system, or is Shopify the master system?
At Nodus Works, we've observed that for the vast majority of omnichannel retailers in Turkey, Nebim is the natural master system, where the true stock levels are maintained. In this setup, Shopify is positioned as a sales channel in front of Nebim; all business rules operate within Nebim.
Integration Setup Process: 4 Stages
Stage 1: Analysis and Data Mapping (1-2 weeks)
- Nebim version and license audit: which API modules are active?
- Product data model analysis: how many SKUs, how many variants, which custom fields?
- Stock location structure: single warehouse or multiple warehouses?
- Order flow: is shipping carrier integration via Nebim or Shopify?
- Is e-invoicing mandatory? Are there B2B orders?
Stage 2: Middleware Development or Configuration (2-4 weeks)
If off-the-shelf middleware is chosen: API keys are configured, field mappings are defined, and data flow is validated in the test environment.
If custom development is chosen: an API integration layer, error management and retry mechanism, and logging system are established.
Stage 3: Testing and Data Validation (1-2 weeks)
- Product transfer test: were 50-100 products from Nebim correctly transferred to Shopify?
- Stock synchronization test: does Shopify update when stock changes in Nebim?
- Order cycle test: test order in Shopify → does it appear in Nebim? → is an e-invoice issued?
- Load test: system behavior when 50 orders arrive simultaneously
Stage 4: Go-Live and Monitoring (1 week)
- Phased rollout: first test with live traffic at low volumes
- Daily log review for the first 30 days
- Stock discrepancy report: Nebim and Shopify stock values are compared daily.
- Error notification: instant alerts for critical errors (order transfer failed, stock update failed).
Common Errors and Solutions
1. Product ID mismatch
The product code in Nebim and the product_id in Shopify may be in different formats. The middleware must maintain this mapping in its own database. If the mapping is broken when a product is deleted and recreated, stock updates will be applied to the wrong product.
2. Stock reset error
If the middleware restarts after a connection loss, the "initial stock synchronization" can reset all Shopify stock to zero. A separate protection layer for "not sending zero stock" is essential in the retry mechanism.
3. Price update delays
When an end-of-season discount is applied in Nebim, it can take hours for prices to reflect on Shopify. This delay can be minimized with high-frequency periodic syncs or webhooks from the Nebim side.
4. Duplicate order creation
The same Shopify order might be sent to Nebim twice due to a network timeout. Using the order number as an idempotency key for each integration request prevents this error.
FAQ
How is Shopify integrated with Nebim?
There is no direct connection; a middleware operates between them. The middleware communicates with Shopify Admin API and Nebim APIs to synchronize product, stock, order, and invoice data bi-directionally. Ready-made SaaS middleware or custom development options are available; the choice depends on order volume and customization needs.
How long does Shopify Nebim integration take?
It ranges from 2-4 weeks with ready-made middleware to 6-10 weeks with custom development. The most critical factors affecting the duration are: Nebim version and API access status, complexity of the product catalog, and e-invoice and marketplace integration requirements.
Is stock updated in real-time from Nebim to Shopify?
It depends on Nebim's webhook support. If supported, stock changes are reflected in Shopify within seconds. If not supported, the middleware performs periodic polling; updates occur every 5-15 minutes. Real-time synchronization is essential during flash sales.
Are orders in Shopify automatically converted into e-invoices?
Yes, with a correctly configured integration, Shopify orders are transferred to Nebim, and Nebim's e-invoice module automatically issues the invoice via the GİB integrator. For B2B orders, the customer's Tax ID (VKN) information must be collected during Shopify checkout.
I use Nebim and Trendyol simultaneously, how do I integrate Shopify?
Position Nebim as the master system. Trendyol and Shopify operate as two separate sales channels connected to Nebim. Stock and order management are handled through Nebim. Do not use a separate Trendyol integration application for Shopify, as conflicting data sources will lead to stock inconsistencies.
Which Nebim versions does Shopify Nebim integration work with?
The integration is applicable to Nebim versions where the API module is active. Nebim 7.x and above generally offer REST API support; older versions use SOAP services. Before starting the project, obtain active API endpoints and version documentation from your Nebim consultant.
How does Nebim stock synchronization work in Shopify?
The middleware queries Nebim's stock API and sends changes to Shopify's inventory_levels/set.json endpoint. For real-time synchronization, a webhook-based trigger is used; if no webhook is available, periodic polling is employed. In a multi-location setup, each Nebim warehouse must be mapped to its corresponding Shopify inventory location.
Which API endpoints are required for Shopify Nebim integration?
On the Shopify side: products, variants, inventory_levels, orders, refunds endpoints. On the Nebim side: product listing, stock inquiry/update, order creation, and e-invoice triggering services. The required endpoints vary depending on the Nebim license package and version.
Which data is required for order transfer from Shopify to Nebim?
Order number, order date, customer information (name, address, email), product SKUs and quantities, price and VAT information, shipping address, and selected shipping method. For B2B orders, the customer's tax identification number (VKN) is mandatory.
Conclusion
If not properly architected, Shopify Nebim integration can lead to critical operational issues such as stock discrepancies, duplicate orders, and invoice delays. When set up correctly, it reduces manual work time per order to almost zero and enables multi-channel sales management through a central ERP.
Contact Nodus Works to design your Nebim + Shopify integration, resolve errors in your existing integration, or restructure your middleware architecture. Let's evaluate Nebim's API infrastructure and Shopify's integration requirements on-site to make the right technical decisions together.
