Shopify Nebim Integration

Nebim is not an accounting program, it is the operating system of a store chain; Shopify becomes one of its sales channels. That is why the real question of the integration is not "will my invoice be issued automatically" but "will the last piece in the store be opened to the site". Setup starts with license preparation and closes with your first order. In between, sellable inventory is separated from raw warehouse quantity, the color and size matrix is translated into Shopify variants, you choose which price list is written to the store, and a brand that ships from store sets the Shopify side up differently.

Talk to us about setup See the integration

200+ active brands
growing on Shopify with Nodus Works

Shopify Nebim integration what is it?

A Shopify Nebim integration is the connection that keeps store orders, customers, products, stock and price lined up with Nebim V3. Because Nebim works with many warehouses and many stores, what is synced here is not a single quantity but which location's stock is opened to the internet.

Setup starts by discovering which version and license pack is in use on the Nebim side; that decides which services are open. Then, because Nebim runs on your own server, a secure access path is opened, sellable inventory and location mapping are decided, and the variant and price-list design is defined. When location mapping goes beyond the standard connection — for example in multi-store and multi-warehouse setups — Nodus Works' Shopify integration and custom app development service builds that mapping for you.

Once the connection is live, Nebim stays at the center: the order comes from the store into Nebim as an order slip, stock and price go from Nebim to the store, and shipping and invoice data are written back. If you ship from store, the multi-location and multi-fulfillment design on the Shopify side also becomes part of this flow.

WHAT SYNCS

What syncs between Shopify and Nebim

Once the connection is live, orders, customers, products, stock, price, shipping and invoices become parts of the same flow. The six headings below cover the questions that come up most often in a Shopify Nebim integration.

Transfer of Shopify orders into Nebim

The order lands in Nebim as an order slip, not as an invoice. Because Nebim's document chain runs as order, reservation, dispatch order, pick, delivery note and invoice, the integration attaches to the start of that chain, not the end.

Nebim Shopify stock sync

Nebim holds the real stock and writes it to the store from there; the store register also writes to the same inventory, so this is a requirement, not a preference. The number that is written is sellable inventory, not raw warehouse quantity.

Price and campaign transfer

Price lists in Nebim are defined per channel and go live automatically at the date and time you set. Which list is written to the store is a setup decision; which side cart discounts run on is also decided separately.

Product, variant and image transfer

The collection is defined in Nebim and transferred to the channel. Color-based images and unlimited product attributes can be carried; against that, marketing copy on the store side has to be marked separately so the integration does not overwrite it.

Shipping and tracking data

Nebim has ready integrations with carriers; when the delivery note and tracking number are written back to the store, the customer notification goes from Shopify. The same order going out in two shipments is also a supported flow.

Invoice and return flow

The document is produced inside Nebim and sent to the official integrator to be sealed. Returns and exchanges run on the Nebim side; writing a store-made return back to Shopify is a link that has to be designed separately.

STOCK

Which stock is written to Shopify?

The most critical decision of the setup is made on the stock side. In Nebim a product's warehouse quantity and its sellable quantity are not the same thing; opening the wrong number to the internet costs more than not opening it at all.

Sellable inventory is not warehouse quantity

Nebim manages sellable inventory separately according to the store's floor, display, count and transfer processes. If the single piece on display, stock locked during a count and a transfer that is on the road are opened to the internet, an oversell chain starts; the number written to the store is sellable inventory.

A reservation has no counterpart in Shopify

When an order is taken, Nebim produces a reservation so the product is not sold to another customer, and it can reserve from more than one warehouse in priority order. On the Shopify side there is only a sellable quantity; if the reserved quantity is not reflected to the store as lower stock, both channels sell the same piece.

Location mapping is the real setup decision

There are three patterns: opening only the ecommerce warehouse is the safest but lowest-revenue path; making the central warehouse and selected stores separate locations is required for omnichannel; writing the total of every location is the riskiest, because it collides with a store sale at any moment.

The sync interval is where the risk sits

If event notification is not set up on the Nebim side, the transfer polls at regular intervals and the minutes in between can collide with a store sale. Discount day and end of season are the moments this gap burns most.

The match is built on every combination's barcode

Nebim can use the product's own barcode and can also produce as many barcodes as you want. The match is not built on the name, it is built on the unique barcode of every color and size combination; if a multi-pack barcode is mixed with a single-sale barcode, stock breaks.

A return puts stock back

A returned product goes back into sellable inventory, but which location that movement writes to matters. A return taken in store enters store inventory; if the number written to the store comes from the ecommerce warehouse, the two sides drift.

All of these decisions are made during setup, because the cost of fixing them later is paid as cancelled orders and lost customers. If your marketplace channels are already tied to Nebim, two transfers reserving the same warehouse's stock separately is an extra risk; the reservation rule of the existing channels should be reviewed before Shopify is added.

SETUP

How is the Shopify Nebim integration done?

The six steps below cover the full setup, from license discovery through the first test order. Some steps run with your team, some with your Nebim partner, so both sides have to be in the process from the start.

Discover the version and license pack

Because a Nebim license is modular, your version and pack decide which services are open. Before a quote is given, the active-module list has to be taken from your Nebim consultant; this is the single item that can delay a project by weeks.

Open a secure access path

Nebim runs on your own server and has no address reachable from outside. Opening the access path together with your IT team is infrastructure work, not integration work, and the first week of the project usually goes here.

Decide sellable inventory and location mapping

Make it clear which location's stock will be written to the store and how sellable inventory is calculated. If you will ship from store, every dispatch location has to be a separate location on the Shopify side.

Set up the variant and barcode design

Translate Nebim's multi-dimension structure into Shopify's three-option limit: usually color becomes a separate product and size becomes a variant. The match is built on every combination's unique barcode, and because this decision sets the whole catalog it is made on day one.

Define the price list and the invoice layout

Open a price list in Nebim that belongs only to internet sales and write that to the store. In the same step also define the separate series for internet-sale invoices, the tax-rate rule and the fields that must appear on the invoice.

Verify the flow with a test order

Place an order with a single product and see that the order lands in Nebim as an order slip, that a reservation is created, that stock drops and that the invoice comes out on the right series. Then return the same order and also check the reverse flow.

The table below shows which Shopify records map to which counterparts on the Nebim side.

What Shopify has	What it maps to in Nebim
Order	Order slip, then reservation and dispatch order
Customer	Deduplicated customer record
Product	Product card
Variant	Color and size combination
Barcode	The combination's unique barcode, the matching key
Location	Warehouse or store
Stock	Sellable inventory
Price	Internet-sale price list
Fulfillment	Dispatch order and delivery note
No Shopify counterpart	Reservation, count lock, loyalty points, displayed piece

The last row of the table is the place most often missed during setup. Reservation, count lock and the piece on display in the store are facts Nebim knows and Shopify does not carry; how they enter the sellable inventory calculation is defined once during setup.

Where are you in the setup?

Tell us about your catalog and current setup, and we will work out how the Shopify Nebim integration should be built for your product structure. You do not need to fill in a form, reach us directly by phone, email or WhatsApp.

Get in touch 0850 888 2815 hub@nodusworks.com WhatsApp

VARIANTS

How is the color and size matrix translated into Shopify?

Nebim sizes variants by industry: in ready-to-wear, color, size, last and drop; in footwear, color, size and width; in furniture, color plus width, depth and height. An unlimited number of colors and sizes can be defined. Shopify, on the other hand, carries at most three options under one product. A color-and-size pair sits comfortably; a four-way matrix does not. This is a real collision that has to be solved during setup.

The established solution is to lift color out as a separate product: the parent product code carries a model, the records under it carry colors, and the variants carry sizes. That way you stay inside Shopify's option limit and every color has its own images, its own address and its own content. Because this decision sets the whole catalog, the collection structure and the addresses, it has to be made on day one; turning back later has a cost on the search-engine side.

The matching key is the barcode, not the name. Nebim can use the product's own barcode and can also produce as many barcodes as you want, and a separate barcode can be assigned to lots such as multi-packs. Every color and size combination must have a unique barcode; mixing a pack barcode with a single-sale barcode is the classic error where stock breaks silently.

Finally, you decide what the integration will not overwrite. Product attributes, color-based images and technical fields come from Nebim; against that, search-engine copy, collection structure and marketing descriptions are not held in Nebim. If those fields are not marked as fields the transfer will protect, weeks of written content are wiped in a single sync.

PRICING

Which price list is written to the store?

Price in Nebim has three layers: prices on the product card, different prices by dimension, and price lists that go live after approval. In Shopify there is a single price per variant. That narrowing is managed during setup.

A separate list is opened for internet sales

The right pattern is to open a price list in Nebim that belongs only to internet sales and write that to the store. When a store or outlet list is attached, the wrong price lands on the site and the customer is usually the one who notices.

The price list goes live at a date and time

Nebim can take a price list live automatically at the date and time you approve, so the campaign calendar can be run by the ERP. Against that, the reflection to the store depends on the transfer interval; at moments such as end of season that interval has to be shortened.

Store-based price differences must not leak onto the site

Nebim lets you set different price groups per store; a different policy can be applied in season and outlet stores. That flexibility is narrowed when it is opened to the internet, otherwise the same product appears at two different prices.

A campaign must not run on both sides at once

Nebim's campaign engine runs cart rules, and Shopify has its own discount engine. If both are on at the same time the discount is applied twice; the practical rule is that price runs from Nebim and cart discounts run from Shopify.

The tax-inclusive versus exclusive split is set from the start

Nebim can hold the price on the product card tax inclusive or exclusive. If you show prices tax inclusive in the store, which value is transferred has to be clear; otherwise a small but constant difference forms on every sale.

Loyalty points do not get a counterpart at checkout

Nebim knows loyalty points, but using points as a payment instrument at the Shopify checkout does not arrive with the integration on its own; that is a separate development. Brands that give points in their stores have to make this expectation clear from the start.

INVOICES

How is an internet-sale invoice issued in Nebim?

Nebim issues the invoice, but the seal is applied outside. On top of that, internet sales have their own rules.

The document is produced in Nebim, the seal is applied at the integrator

The invoice is formed inside Nebim, sent to an officially approved special integrator, sealed, and the number comes back. If the buyer is an e-invoice taxpayer an e-invoice is issued, otherwise an e-archive. In cloud pre-accounting programs both sit under the same roof, so the difference here means a separate party on the project.

Internet-sale invoices go on a separate series

The series of invoices for sales made over the internet must be different from your other invoices. When Shopify orders are written to the same series as store sales, the layout does not meet the regulation and a retrospective correction is not possible.

The invoice has extra fields that are required

The web address where the sale was made, the payment method, the organization that mediated the payment, the payment date, the tax or identity number of the party that carried the goods, the ship date, a returns section and a statement that the sale was made over the internet must be present. Those fields filling in depends on the transfer reading them from the order.

The paper copy goes into the parcel

So the returns section can be filled in, the paper copy of the invoice is expected to go with the shipped goods. The store's packing slip does not replace this; so this rule changes the packing-station flow directly.

Cancellation and returns are separate jobs

Nebim can cancel an order in full or in part and records the cancellation reason. On an order that has been invoiced, if the cancellation window has passed a return invoice is required; tying the two cases to the same flow breaks the account balance.

A corporate account is not opened until invoice fields are collected

The Shopify checkout does not collect tax ID, tax office and legal title by default. If those fields are not collected, every order is treated as an end consumer and the right document cannot be issued to a corporate customer.

OMNICHANNEL

What does ship-from-store change on the Shopify side?

This is where Nebim really sets itself apart: opening store inventory to the internet, dispatching the order from the nearest store and delivering the same order from more than one location are established capabilities. That has three concrete counterparts on the Shopify side.

Every dispatch point has to be a separate location

If you will dispatch the order from a store, that store has to be a separate location on the Shopify side. This scenario cannot be built on a setup that runs on a single total stock, because which point the order will leave from is never known.

The order closes with multiple fulfillments

Because products on the same order can leave from different locations, the order closes with more than one fulfillment, not a single fulfillment record. Split shipment is a supported flow, but this design has to be built from the start on the Shopify side.

One order can have two different invoices

Invoices for the same order can be issued from different locations. That means a one-to-one relationship cannot be built between order number and invoice; the accounting match has to be designed for that.

There is a counterpart for reducing oversells

Opening the whole firm's inventory to the internet reduces oversells, and shipping from the nearest point speeds delivery and lowers shipping cost. Against that, opening the single piece in the store to the internet means accepting the risk of colliding with a store sale.

The store-return link is built from the start

When a customer returns a product they bought online at a store, if the Shopify order does not close, revenue and stock reports drift. Nebim knows the return; writing it back to the store is designed separately, and this is the link the integration skips most often.

The customer is recognized as the same person on both channels

Nebim deduplicates the customer record on defined fields, so you can also recognize a customer who shops in store on the internet. Which field is matched to the Shopify customer is decided during setup; that decision also directly affects whether the loyalty side works.

None of these three counterparts is a setting you can add later; the location and fulfillment design sits on top of the catalog and the order flow. If channels such as Trendyol and Hepsiburada also use the same inventory, the reservation rule has to run from one place; you can review Station on its page to see stock, price and orders from a single panel.

COMMON MISTAKES

The most common mistakes in the Shopify Nebim integration

The nine headings below are the mistakes that come up most often in setup. The results look alike too: oversells, the wrong price, a report that does not tie, or an architecture that changes in the middle of the project.

Writing raw warehouse quantity to the store

When the displayed piece, the count lock and the transfer on the road are not subtracted, stock that cannot be sold is opened to the internet. The oversell chain starts here and the cost is paid in cancelled orders.

Leaving license discovery until after the quote

Which services are open depends on the version and license pack. A timeline given without the active-module list does not hold, and the project is delayed by weeks.

Treating the access path as integration work

Nebim runs on your own server and not a single line of data flows until secure access is opened. This is infrastructure work; if the IT team is not in the project from the start, the first week is wasted.

Trying to fit a multi-dimension variant into one product

Shopify carries at most three options on one product. If the color-as-a-separate-product decision is not made on day one, the catalog has to be rebuilt and a cost appears on the search-engine side.

Attaching a store price list to the site

When an outlet or store list is attached, the wrong price lands on the site. Opening a separate list for internet sales closes this from the start.

Leaving the campaign open on both sides

When Nebim's campaign engine and Shopify's discount engine run at the same time, the discount is applied twice. Which side price and cart discounts run on has to be written down.

Writing internet sales onto the same invoice series

Internet-sale invoices must use a separate series, and the invoice must carry a returns section and the required statement. Putting the paper copy into the parcel is also part of the same rule.

Leaving store returns outside the flow

If the Shopify order does not close when the customer returns in store, the revenue report swells and stock drifts. This link has to be designed from the start.

Not reviewing the marketplace reservation rule

When two transfers reserve the same warehouse's stock separately, the same piece is sold on two channels. Existing rules have to be reviewed before a new channel is added.

SCENARIO

Three common problems and how they were solved

The three setup scenarios below show how we handled Shopify Nebim integration problems we solved in stores we connected.

A product sold online not being found in the store

ProblemOrder volume rose quickly after setup, but the packing team could not finish more than a few orders a day. The product was in the system, not on the shelf; as cancellations grew, the customer-service load grew too.

CauseRaw warehouse quantity was being written to the store. Pieces on display in the store, stock locked during a count and transfers on the road between locations were inside that number; so a quantity that could not be sold had been opened to the internet.

SolutionThe transfer was changed to read sellable inventory, and displayed pieces and count locks were left out of the calculation. Location mapping was rebuilt and the cancellation rate returned to normal inside the first month.

Sizes being listed as separate products

ProblemThe catalog was transferred to the store and products went live, but every color-and-size combination of the same model sat on its own page. The customer could not pick a size, and collection pages filled with hundreds of records and became unreadable.

CauseNebim carries variants with color, size and extra dimensions; Shopify accepts at most three options on one product. Because that translation was not done during setup, every combination had been sent as a separate product.

SolutionThe catalog was rebuilt so color was a separate product and size was a variant, and the match was tied to every combination's unique barcode. Color-based images were attached to the right product, duplicate records were closed and a redirect plan was produced for the old addresses.

Store-made returns not landing in the reports

ProblemAt month end the gap between internet revenue and collections grew. A surplus also appeared in the stock count; why the two tables drifted was not clear at first glance.

CauseCustomers were returning products they bought online at the store. Nebim was posting the return and the stock movement, but because that data was not written back to Shopify the orders kept looking completed.

SolutionThe store-return link was built: when the return is posted in Nebim the related Shopify order also closes and the stock movement writes to the right location. The revenue report and collections lined up, and the count difference also disappeared.

STATION

Shopify Nebim integration

Station is the tool we built to watch the stock, price, order and fulfillment flow from a single panel. When marketplace channels are added, Nebim stays at the center.

See the integration Talk to us about setup

FAQ

Frequently Asked Questions

How is the Shopify Nebim integration done?

Setup starts by discovering which version and license pack is in use in Nebim; that decides which services are open. Then, because Nebim runs on your own server, a secure access path is opened, sellable inventory and location mapping are decided, the variant and barcode design is set up, and a separate price list and invoice series are defined for internet sales. The last step is verifying the flow with a test order placed with a single product.

Does Nebim V3 connect to Shopify directly?

It does not. Nebim runs on your own server and has no address reachable from outside, so a layer sits in between. Nebim offers a service layer on its side, and the party that builds the connection is an application that uses that layer or a project-specific middleware. Opening the secure access path is also the first setup step.

Does Nebim have an official Shopify app?

Nebim has not published an app of its own in the Shopify App Store; the app found there belongs to an independent developer. The path Nebim has officially announced is building an integration through its own service layer. Shopify also does not appear by name on the ecommerce-systems list Nebim has published; that does not mean it is unsupported, it means a ready connector written for Shopify has not been announced.

Which path should I choose: an app, an integrator panel, or custom development?

The three fit different scales. A ready app is the fastest path to set up at low and mid volume and covers standard flows. A multi-channel integrator panel makes sense when you want to collect Shopify in the same place as your marketplaces. If ship-from-store, multiple locations and custom business rules are required, project-specific middleware is needed; the choice among the three is made against your scale and your omnichannel expectation.

How is stock transferred from Nebim to Shopify?

Nebim holds the real stock and writes it to the store from there; the store register also writes to the same inventory, so this is a requirement, not a preference. The important detail is that the number written is sellable inventory, not raw warehouse quantity: the piece on display in the store, stock locked during a count and a transfer that is on the road stay outside this calculation.

What is the difference between sellable inventory and warehouse quantity?

Nebim manages sellable inventory separately according to the store's floor, display, count and transfer processes. Warehouse quantity is the physical total sitting there; sellable inventory is what can actually be sold and shipped. Opening warehouse quantity to the internet means putting stock that cannot be sold up for sale, and that is the most common cause of an oversell.

How does a Nebim reservation land on Shopify?

When an order is taken, Nebim produces a reservation and stops the product being sold to another customer; it can also reserve from more than one warehouse in priority order. On the Shopify side the counterpart is only a sellable quantity. If the reserved quantity is not reflected to the store as lower stock, both channels sell the same piece.

How is multi-warehouse and store stock written to Shopify?

You pick one of three patterns. Opening only the ecommerce warehouse is the safest but lowest-revenue path. Making the central warehouse and selected stores separate locations is the path required for ship-from-store. Writing the total of every location is the riskiest, because it collides with a store sale at any moment. The decision is made on the project and changing it later touches the catalog and the order flow.

How do size and color variants match?

Nebim carries variants with color, size and extra dimensions by industry; Shopify accepts at most three options on one product. The established solution is to lift color out as a separate product and leave size as a variant. That way every color has its own images and its own address. Because this decision sets the whole catalog, it has to be made on day one.

Which field are products matched on?

The match is not built on the name, it is built on the unique barcode of every color and size combination. Nebim can use the product's own barcode and can also produce as many barcodes as you want, and a separate barcode can be assigned to lots such as multi-packs. Mixing a pack barcode with a single-sale barcode is the classic error where stock breaks silently.

Are product images and descriptions also transferred?

Color-based images and product attributes can be transferred from Nebim. Against that, search-engine copy, collection structure and marketing descriptions are not held in Nebim; those fields have to be marked as fields the transfer will protect. Otherwise weeks of written content can be wiped in a single sync.

Which price list should be written to the store?

Opening a separate price list in Nebim that belongs only to internet sales and writing that to the store is the right pattern. When a store or outlet list is attached, the wrong price lands on the site. Because Nebim can take a price list live automatically at the date and time you approve, you can also run the campaign calendar from the ERP.

Do Nebim campaigns also run on Shopify?

Nebim's campaign engine runs cart rules, and Shopify has its own discount engine. If both are on at the same time the discount is applied twice. The practical rule is that price runs from Nebim and cart discounts run from Shopify; items such as loyalty points are solved separately because they have no counterpart at checkout.

Can loyalty points be used at the Shopify checkout?

Nebim knows points and can merge the store and the internet store under the same customer, but using points as a payment instrument at the Shopify checkout does not arrive with the ERP integration on its own; that is a separate development. Brands that give points in their stores have to make this expectation clear before setup.

Do Shopify orders land in Nebim as an invoice or as an order slip?

They land as an order slip. Nebim's document chain runs as order, reservation, dispatch order, pick, delivery note and invoice, and each step is derived from the one before it. So the integration attaches to the start of that chain, not the end; the invoice forms as the natural result of the chain.

Are Nebim e-invoices and e-archives issued automatically on a Shopify order?

They are. The document is formed inside Nebim, sent to an officially approved special integrator, sealed, and the number comes back; if the buyer is an e-invoice taxpayer an e-invoice is issued, otherwise an e-archive. So the document is produced in Nebim but the seal is applied outside. In cloud pre-accounting programs both sit under the same roof, so the difference here means a separate party on the project.

Is a separate series required for internet-sale invoices?

Yes. The series of invoices for sales made over the internet must be different from your other invoices, so they are not written to the same series as store sales. This split is set at the very start of the invoice layout; the series of past invoices cannot be changed later.

Which information must appear on an internet-sale invoice?

The web address where the sale was made, the payment method, the organization that mediated the payment, the payment date, the tax or identity number of the party that carried the goods, the date the goods were sent, a returns section and a statement that the sale was made over the internet must be present. The paper copy of the invoice is also expected to go with the shipped goods; the store's packing slip does not replace this. This rule also changes your packing flow.

How is corporate invoice data collected?

The Shopify checkout does not collect tax ID, tax office and legal title by default. When those fields are not collected, a corporate customer record cannot be opened on the Nebim side and every order is treated as an end consumer. If you sell to companies, where these details will be collected in the payment flow has to be solved during setup.

Can the same order have two separate invoices?

It can. In setups that ship from store, products on the same order can be delivered from different locations and their invoices can also be issued from different locations. That means a one-to-one relationship cannot be built between order number and invoice; the accounting match has to be designed for that.

What is required on the Shopify side for ship-from-store?

Three things are required: every dispatch point being a separate location on the Shopify side, the order being able to close with more than one fulfillment instead of a single fulfillment, and the accounting match accepting that one order can have more than one invoice. This scenario cannot be built on a setup that runs on a single total stock.

Does a store-made return land on Shopify?

It does not land on its own; this link has to be built separately. Nebim posts the store return and the stock movement, but if the data is not written back to Shopify the order keeps looking completed; the revenue report swells and stock drifts. This is exactly the link the integration skips most often.

Does a Shopify integration also work with Nebim Winner?

The answer depends on which services the product you hold offers; which services are open on the Nebim side is decided by the version and license pack. That is why the first step is always taking the active-module list from your Nebim consultant. If there is no service layer, a different path has to be designed for the connection.

How long does the integration take?

This is a project timeline, not a setup day. Four things set the duration: license discovery, opening the secure access path, deciding sellable inventory and locations, and setting up the variant translation. Because the access path is IT work, the first week of the project usually goes there.

Can marketplace orders also be transferred to Nebim?

They can, and at most brands they already are; Shopify is added to that table as one more channel. Two risks then appear: the same warehouse's stock being reserved separately by two transfers, and the same order opening a slip twice. The reservation rule of the existing channels should be reviewed before a new channel is added.