Sitoo’s pitch is unified commerce — one platform running in-store POS, online orders, and omnichannel routing rather than bolting separate systems together. That’s genuinely useful for the retailers who adopt it, mostly in Europe, but it also means a lot of order and inventory logic already happens inside Sitoo before NetSuite ever sees it. Integrating the two well means respecting that, not duplicating it.
Sitoo already does the routing — NetSuite needs to keep up
Click-and-collect and ship-from-store are Sitoo’s reason for existing as a unified platform, and both depend on inventory visibility across every location in near real time. If NetSuite is your financial and inventory system of record, its stock data has to feed Sitoo’s order-routing logic accurately, and Sitoo’s fulfillment decisions have to flow back cleanly. The failure mode here isn’t dramatic — it’s a slow drift where Sitoo’s routing engine starts making decisions on inventory numbers that are a few hours stale, and customers get told an item is available for pickup when it isn’t. The integration exists specifically to prevent that drift, which means the sync frequency and conflict-resolution logic matter more than they would for a simpler, single-channel retailer.
European VAT and multi-currency aren’t an afterthought
Because Sitoo’s customer base is concentrated in Europe, most of these integrations have to handle VAT and multi-currency correctly from the start rather than as a later add-on. That touches how transactions post to NetSuite’s GL, how tax is calculated and reported per jurisdiction, and how currency conversion is handled if a retailer operates across multiple European markets with different functional currencies. This is one of the areas where getting the financial mapping wrong doesn’t show up immediately — it shows up at tax filing time or during an audit, which is a much more expensive time to discover it.
Loyalty and customer data need one home
Sitoo carries in-store and online customer and loyalty data as part of its unified model. For that to actually mean something once NetSuite is in the picture, customer records need to reconcile between the two systems rather than existing as separate profiles that happen to share a name and email. A loyalty program that doesn’t see a customer’s full purchase history across channels isn’t really unified — it’s just two systems with a shared login.
Returns need to ignore which channel a sale started on
A unified commerce platform is supposed to make channel invisible to the customer — buy online, return in store, or the reverse, without friction. That only holds up if the integration treats a return the same way regardless of where the original sale happened. If NetSuite’s inventory and revenue adjustments depend on matching a return to the right original transaction, the sync needs to preserve that link across channels reliably, not just within whichever channel the sale originated in.
What moves between the systems
A Sitoo to NetSuite integration generally covers:
- POS and online transactions
- Inventory across all locations
- Customer and loyalty data
- Order routing for click-and-collect and ship-from-store
- Returns, matched against the original transaction regardless of channel
Where we start
Because Sitoo installations vary by market and by how much of the omnichannel routing a retailer actually uses, we start by mapping what’s really happening operationally — which locations fulfill which order types, what VAT and currency requirements apply, and how loyalty data is currently structured — before deciding how NetSuite should plug in.
For the full technical breakdown, see the complete Sitoo integration guide, or contact us if you’re running Sitoo across multiple European markets and want a straight assessment of what integrating it with NetSuite would actually take.