Shopify Netsis Integration

A Shopify Netsis integration is a bridge that connects the product, stock, price and invoice records in Netsis to Shopify. Netsis has two separate architectures: Netsis 3 (Standard/Enterprise) and Wings/Wings Enterprise. Which one you use directly sets the integration method: REST API, SOAP web service, NetOpenX or a direct database connection. The first setup decision is which connection path your Netsis version supports. The integration tool is chosen after that.

Talk to us about setup See the integration

200+ active brands
growing on Shopify with Nodus Works

Shopify Netsis integration what is it?

A Shopify Netsis integration is the connection that writes your store's orders and stock movements into the customer account, warehouse and invoice records in Netsis. Netsis does not publish a Shopify app of its own. An integration tool builds the bridge, and it runs through the NetOpenX interface, a REST or SOAP web service, or a database connection.

Setup starts with version discovery, before any code is written. On the Netsis Enterprise version, API support is the widest. On the Standard version, the integration usually runs through NetOpenX or a direct database connection. A setup that does not know this split starts with the wrong integration method and stalls at the connection stage.

Once the connection is live, daily work runs from one screen. The order lands in Netsis as a customer-account entry, and stock is updated in both directions. When the invoice is issued, that information comes back to the Shopify side. To make it clear which connection path works on your version, you can get support from Nodus Works' Shopify integration and custom app development service.

DATA FLOW

What syncs between Shopify and Netsis

Once the connection is live, six data groups flow regularly between the two systems. Which interface carries that flow in Netsis changes with the version: NetOpenX, a web service or the database. The data groups that move stay the same.

Transfer of Shopify orders into Netsis

The order is written into Netsis as a customer-account entry. If there is no customer record, the integration tool opens a customer account first, then attaches the order to that account.

Netsis Shopify stock sync

A warehouse movement is read from Netsis and written to Shopify, and the reverse direction works as well. The sync interval changes with the connection method in use, an API or a database query.

Price and campaign transfer

The price list in Netsis is written to Shopify. If a price list that belongs to internet sales is not defined separately, an in-store campaign can leak onto the site.

Product and variant transfer

The item card and the variant data in Netsis are translated into the Shopify product structure. Barcode matching is the foundation this translation is built on.

Shipping and tracking data

Shipping integration is the job of the carrier you use, not of Netsis. The shipment record that comes from Netsis updates the order status in Shopify.

Invoice and return flow

The invoice is issued in Netsis and sent to GİB through the e-invoice and e-archive integrator. Cancellation and returns are handled separately in Shopify, and they do not automatically correct the customer-account entry in Netsis.

STOCK

Which stock is written to Shopify?

Warehouse quantity in Netsis and the sellable quantity that should be written to Shopify are not the same thing. Integrations that do not build this split stay open to overselling.

Sellable inventory is not warehouse quantity

Stock that is reserved, or set aside for a corporate order, shows in the warehouse quantity but is not sellable. The number written to Shopify should be the quantity left after that difference is removed.

Location mapping is the real setup decision

If you have more than one warehouse or branch, which location connects to Shopify has to be clear at the start. When that decision is changed later, past stock data can look inconsistent.

The sync interval is where the risk sits

Stock does not update instantly. It updates at the working frequency of the connection method in use: an API, a web service or a database query.

The match is built on the barcode

The item card in Netsis matches the Shopify variant on the barcode. A card with a missing or repeated barcode drops that variant out of the sync.

A return puts stock back

A return processed in Netsis puts sellable stock back. If this movement is not written to Shopify, the quantities on the two sides drift apart over time.

MULTICHANNEL SALES

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

In businesses with a physical store, a shipment can leave from a store location as well as from the warehouse. In Netsis, every dispatch point has to be defined as a separate location or branch. Otherwise the Shopify side does not correctly show which location the goods left from.

A sale or a return made in the store is a movement that should change the stock view in Shopify. If this movement does not flow automatically from Netsis to Shopify, store sales never appear in the online stock. The last units then stay open to overselling.

One order may be fulfilled from more than one location. During setup, account for a single Shopify order mapping to more than one dispatch record on the Netsis side.

SETUP

How is the Shopify Netsis integration done?

The six steps below cover the full setup, from version discovery until the first order lands in Netsis. The first two steps are specific to Netsis: until you choose the right architecture and the right connection path, the later steps do not work.

Discover which Netsis architecture you use

Make it clear whether you use Netsis 3 (Standard/Enterprise) or Wings/Wings Enterprise. These two architectures use different integration methods. Trying to set one up with a tool chosen for the other stalls the setup from the start.

Choose your connection path: NetOpenX, web service or database

On the Enterprise version, the REST API through NetOpenX offers the widest support. On the Standard version, a SOAP/XML web service or a direct database connection is more likely. Confirm with your partner which path is open on your license.

Confirm the NetOpenX setup and license

If you will use the REST API, NetOpenX comes in a separate setup package and runs on the server as a Windows service. Confirm that this service is installed and running before setup.

Enter your session details

To connect to Netsis, a session is opened with the user name, password, company, branch and accounting period. When that session expires, it has to be opened again. You get these details from your partner or your system administrator.

Map the warehouse, customer account and price list

This step defines which Netsis warehouse connects to Shopify, which customer-account code new orders open under, and which price list belongs to internet sales.

Verify the flow with a test order

Create a single order and check that the customer-account entry lands in Netsis, that the stock drop works in both directions, and that the Shopify side updates when the invoice is issued.

Where are you in the setup?

Tell us about your catalog and your current Netsis setup, and together we will work out how the Shopify Netsis integration should be built for your architecture. 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

AGREEMENT AND ACCESS

Where do you get the Netsis integration details?

The answer to this question splits in two in Netsis, by version. On an Enterprise license, the REST API can be used through NetOpenX, and that interface comes in a separate setup package and runs as a Windows service. On a Standard license, the integration usually runs through a SOAP/XML web service or a direct database connection.

You get the connection details (user name, password, company code, branch code and accounting period) from your Netsis partner or your system administrator. Netsis has no single central developer portal that is open to the general user. Choosing an integration tool before your partner confirms which connection path is active on your license carries the risk of starting setup with the wrong method.

When the opened session expires, a new sign-in is required. During setup, check whether your integration tool renews that session automatically. If it does not, sync can stop silently.

COMMON MISTAKES

The most common mistakes in the Shopify Netsis integration

Choosing an integration tool before the architecture is confirmed

Netsis 3 and Wings use different integration methods. A tool chosen before this split is clear tries to point the setup at the wrong connection path.

Assuming the NetOpenX service is running

The REST API depends on a separate Windows service being installed and active. When that service stops, the integration cuts off the data flow silently.

Attaching the in-store price list to the site

If a price list that belongs to internet sales is not defined separately, an in-store campaign or a staff discount can leak into Shopify.

Not checking who is responsible for renewing the session

If the session is not renewed when it expires, sync stops. This is usually noticed only after a stock mismatch appears.

Assuming a variant without a barcode will sync

The item card in Netsis matches the Shopify variant on the barcode. A card with no barcode, or with a repeated one, breaks stock sync for that variant from the start.

Forgetting to correct the return and cancellation by hand in Netsis

An order cancelled in Shopify does not automatically correct the customer-account entry in Netsis. If this match is not built, customer-account balances drift from the real position over time.

Assuming a third-party screen belongs to Netsis itself

On variants and barcodes, some sources are actually talking about a separate product called "netsim". A match built for the wrong screen produces an error on the live system: the field was not found.

Not fixing a price-list number to the internet channel

If setup does not state clearly which number, such as Price List 1, 2 or 3, belongs to internet sales, an in-store campaign price can be written to Shopify by mistake.

VARIANT, PRICE, INVOICE

How do color, size and the price list work in Netsis?

In Netsis, multiple price lists (Price List 1, 2, 3...) and foreign-currency price definitions can be matched in the integration layer, and that part has been confirmed. A separate standard that officially defines which price list belongs to internet sales was not confirmed in the sources. You have to make this split clear in your own setup, together with your partner.

On the variant and barcode side, some third-party sources mention a structure called "Dinamik Stok Tipi" (Dynamic Stock Type, DST). It is not clear whether this information belongs to Netsis itself or to a separate product called "netsim". Before you build barcode matching, confirm with your partner which screen you use, and do not go forward on an assumption built from this uncertainty.

On the invoice-series side, an old source mentions a special setting that makes the series of the invoice number variable. Whether this setting is still valid on current versions was not confirmed. If you need a separate invoice series per branch, you have to set it up with your partner in a way that fits your version.

STATION

Shopify Netsis integration

Station is the tool we built to watch the order, stock, price and invoice flow from a single panel. When marketplace channels are added alongside Netsis, every channel's order is written into the same customer-account, warehouse and price-list layout.

See the integration Talk to us about setup

FAQ

Frequently Asked Questions

Does Netsis have an official Shopify app?

No. Netsis does not publish a Shopify app of its own. The connection is built with a third-party integration tool that runs through NetOpenX, a web service or a database connection.

How does the difference between Netsis 3 and Wings affect the integration?

The two architectures use different connection methods. On Wings/Wings Enterprise, the REST API through NetOpenX is supported more widely. On Netsis 3 Standard, a SOAP web service or a database connection is usually preferred.

Is a separate license required for NetOpenX?

Using the REST API requires an active integration license, and NetOpenX comes in a separate setup package. Confirm with your partner whether this package is active on your license.

Will the forum information I found work on the current version?

There is no single, current documentation source for Netsis that is open to the public. Forum posts and old blog information can lose their validity depending on the version. Do not apply them before setup unless your partner has confirmed them.