The setup

There is one setup, and it lives on the app's Home until you go live: Before you start, then SAGE connection, Stores, SAGE items, Payments, Printing & delivery and Go live, each row with one state. Under them, the optional pages: Tax Free, Salespeople, Document design and Online returns and exchanges. Home shows how many are done and a Continue button to the next one.

After go-live the same list stays under Settings › Setup steps, so any part can be changed later. Settings itself lists every part of zrsPOS as its own page, each with its state.

The steps

• Before you start: what to have ready outside zrsPOS, with the page for your SAGE partner.
• SAGE connection: the SmartAPI address and key; zrsPOS reads your company, NIF and licence.
• Stores: which Shopify locations sell at a till, and how each one invoices (série, documents, tills).
• SAGE items: the SAGE items zrsPOS books what isn't a product on (custom sales, refunds, shipping), and the barcode check.
• Payments: which SAGE payment method each Shopify payment method becomes.
• Printing & delivery: who prints, the printers, and how documents reach the customer.
• Go live: what still blocks, the plan, a real test document, the switch day and Go live.

A step that reads your SAGE stays locked, with "Connect SAGE first", until SAGE answers a test of the saved connection.

Optional pages

Tax Free, Salespeople, Document design and Online returns and exchanges. They never block going live. Your plan is chosen on its own page, and Go live links to it.

The states

Every row shows exactly one state, and Home, the step page, Settings and Go live always agree, because one check decides them all.

Working never comes from "a value was saved". It comes from asking SAGE, Shopify or the tablets, and zrsPOS checks again on its own every 30 minutes once you are live. The rule for each part is in What Working means. A part that was Working can fall back to Needs attention later, for example when someone deactivates a série in SAGE.

With more than one store, the checks run per store. Stores that zrsPOS doesn't invoice are shown greyed, never as a problem.

A step page

Each step is a short page: what it is for, then one row per thing it needs, each with its state and opening its own page (where the settings are). The step is Done when every row is. Back and Next go through the steps in order.

How zrsPOS treats your SAGE

zrsPOS never changes your SAGE silently. Whenever it can create something for you (an item, a payment method, a till), it follows the same four moves:

1. Proposes: it shows exactly what it will create.
2. You confirm with one button that names it.
3. It writes, showing each step.
4. It reads the record back from SAGE and checks every field it depends on. Only then is it Working.

For what SAGE's API cannot do (creating a série, registering it with the AT), zrsPOS gives you a guided task with exact steps for you or your SAGE partner, then a Check again button.

Order and dependencies

• SAGE comes first: everything else reads your SAGE (séries, items, payment methods).
• Every store has its own settings. There is no shared default: a store invoicing on another store's série is a mistake nobody would notice on the document.
• Shopify is the price authority. Every document line carries the price from Shopify; the price on a SAGE item never matters.

Language

The app follows the language of the Shopify user using it (Portuguese or English). Documents have their own language, set in Document design.