What does this integration do?
The critical decision in a Nebim V3 integration is which system is the master. In multi-channel retail, stock truth is usually held in Nebim, with Shopify positioned as a sales channel in front of it. We build the integration by settling that architectural decision first, heading off the risk of dual sources and stock conflicts.
The data it synchronises
Product and variant transfer
Stock and price synchronisation
Order → Nebim order record
Customer account matching
e-Invoice triggering
Multi-warehouse stock management
How the data flows
01
The master system decision
Which system owns which data: stock and price usually in Nebim, content and imagery in Shopify. We do not write a line of code until that decision is in writing.
02
Product and variant matching
The matching key is the stock code and barcode. The colour/size structure on the Nebim side is mapped to Shopify variants, and an exception list is kept for records that do not match.
03
Stock and price flow
Stock and price are written from Nebim to Shopify at regular intervals. Frequency is raised for fast-moving products and lowered across thousands of static ones to protect the request budget.
04
Order flow back
The Shopify order becomes an order record in Nebim; the customer account is matched, and payment and shipping data are carried across.
05
Invoicing and returns
The invoice is issued on the Nebim side; on returns and cancellations, writing stock back and cancelling the invoice run in the same flow.
What we watch for in this integration
Stock must have a single owner: setups holding stock in Shopify, Nebim and a marketplace panel all at once produce overselling
The split between retail store stock and ecommerce stock has to be clear; which warehouse counts as sellable stock is a commercial decision
A safety buffer (holding a set quantity back from the sync) is the single most effective measure in multi-channel setups
Sync frequency and rate limits are planned ahead of campaign periods
Manual stock corrections made in Nebim must be logged; otherwise the source of a discrepancy cannot be found
The setup process
01
Data and permission analysis
We decide which data flows in which direction, which system is the master, and what API permissions are required.
02
Mapping table
Product, variant, category, warehouse and account fields are mapped between the two systems, one by one.
03
Development and testing
The integration is built on a development store; order, return and error scenarios are tested with real data.
04
Going live
It is released through a controlled switchover, watched closely for the first few days, with the error queue monitored.
05
Monitoring and maintenance
Logging, error alerting and API version updates continue under the maintenance retainer.
What we need from you before we start
Nebim V3 version and access method (service/database)
Which tables hold the product, stock and price fields
Warehouse/store structure and which warehouse is opened to ecommerce
The customer matching rule and invoice flow
Product count and daily order volume