Your store and online channel, one live inventory.

Sitoo is a cloud-native POS system. It runs in the browser, stores its data in the cloud, and syncs with your ecommerce platform in real time. For retailers managing both physical stores and an online channel, the core challenge is data consistency. When a customer wants to return an online purchase in-store, the POS needs to know about that order. When a product sells in-store, your website needs to reflect that stock change before another customer orders it online. When a customer places a click-and-collect order, your store staff need to see it at the till before the customer arrives to pick it up.

Sitoo handles the in-store side of this. The question is always what it connects to and how well those connections hold under real operating conditions.

Where Sitoo sits in your stack

A Sitoo setup involves at least three systems: the POS itself, an ecommerce platform, and typically an ERP or central inventory management system. Sitoo sits at the intersection of the physical store and your wider commerce infrastructure. It records in-store transactions, manages staff and till access, processes returns, and passes data upstream to the systems that track inventory and orders at scale.

The ecommerce platforms we work with — Norce, Shopware, Shopify, and Magento with Hyvä — each have integration paths to Sitoo. How deep those connections go varies. Norce, as a headless commerce engine with strong Nordic retail credentials, tends to suit Sitoo deployments where inventory control and multi-store logic are central. Shopify provides a faster path if your catalogue is smaller and your store footprint is more straightforward. Shopware and Magento each bring their own strengths depending on catalogue size, customization needs, and team capacity.

The platform choice shapes what the Sitoo integration looks like. We evaluate this early and make sure the decision is grounded in your actual store format, catalogue, and operational model rather than in platform preference.

The three omnichannel flows that determine real-world function

Three flows define whether unified retail actually works in practice: click-and-collect, in-store return of online orders, and ship-from-store.

Click-and-collect requires that an online order appears at the point-of-sale before the customer arrives, and that the POS closes that order correctly when the customer picks it up. In-store returns of online orders require that the POS looks up the original online order, processes the return, and triggers the correct refund flow back through the ecommerce platform. Ship-from-store requires that in-store stock is visible to the online channel and that store staff can pick, pack, and dispatch an online order from their till.

Each of these flows requires data to move correctly between Sitoo and your ecommerce platform. None of them work out of the box without an integration designed for them. We scope this during discovery before any build work begins.

Data model alignment

Most integration problems in POS projects come from data model mismatches rather than connector failures. If your in-store SKU structure does not match your online SKU structure, stock sync produces errors. If your pricing rules in the POS use different logic than your ecommerce platform, promotions behave unpredictably at the till. If your customer records use different identifiers across systems, loyalty and CRM data does not unify cleanly.

We review data models early in every engagement. This is upstream work that does not feel like the exciting part of a project, but it is what determines whether the integration holds in production. If your current ERP uses a different product hierarchy than your ecommerce platform, we surface that during discovery rather than after go-live.

For retailers adding a loyalty or CRM layer alongside Sitoo, data model alignment becomes even more critical. In-store purchases need to feed loyalty points, and those points need to be redeemable online. That requires consistent customer identity across the POS, the ecommerce platform, and the CRM layer. If you are evaluating loyalty platforms alongside POS, Voyado is a platform that connects closely with Sitoo in this context and is one we implement.

What a Sitoo project involves

A Sitoo engagement at Nordic Web Team is not an isolated integration task. It sits inside a broader commerce delivery that covers platform selection, architecture design, frontend development, content work, and launch planning. The POS integration is one workstream — important, but not separate from the rest.

We start with discovery: reviewing your current stack, your store format, and what you are trying to achieve. We document the data flows your specific scenario requires, whether that is two stores with a Shopify frontend or twelve stores with a Norce-based multi-market setup. Then we design the architecture, build and test all flows, and plan a go-live that covers both online and physical channels in parallel.

Post-launch, we hand over documentation and make sure your team understands the integration: what it does, where it connects, and how to maintain it. A well-designed setup should not require permanent agency involvement to function.

Who this is for

This approach fits fashion retailers, specialty retailers, and multi-brand retailers who are building omnichannel capabilities for the first time, replacing a legacy POS that is not connected to their ecommerce platform, or adding the ecommerce layer to an existing Sitoo setup. It also fits retailers who have both sides running but without a clean integration between them.

If you are evaluating your next step, the right starting point is a clear picture of what you currently have and what needs to connect to what. That is where we begin.