How the platform is organised

Serat is one system with several front doors. Everything reads and writes the same catalogue and the same stock ledger, which is the reason a sale at the till changes what the online channel can promise.

The shared core

Two records sit underneath everything else. The first is the variant: a specific style in a specific colour and size, with its own barcode and prices. Nothing in Serat moves stock for a style in the abstract; movements always name a variant.

The second is the stock movement: an append-only record of a quantity change at a location, with its reason and origin. Current stock is the sum of movements rather than a number someone typed. That is what makes a disagreement about stock answerable instead of an argument.

The back office

This is where the catalogue is maintained, prices are set in bulk, labels are printed, stocktakes are opened and reviewed, transfers are created, and reports are read. It is the only area where destructive changes to the catalogue are possible, and access to it is role-based.

The point of sale

A till screen intended for a counter with a scanner and a receipt printer. It looks up variants by barcode, applies per-line discounts, splits a payment across cash and card, and processes returns and exchanges against the original sale. Every completed sale writes stock movements at the selling location immediately.

The fulfilment queue

Orders from connected channels appear in one list. Depending on the channel and workspace settings, Serat can plan a fulfilment location, identify stock that needs a transfer, and support picking and courier paperwork. Review the order's actual plan and available actions rather than assuming every step happens automatically.

The wholesale portal

Wholesale runs as its own storefront with its own logins, because the people using it are your clients rather than your staff. It shows an approved projection of your catalogue at the prices and discounts assigned to each client, and it is where they place size-run orders. Orders and catalogue changes can take time to appear in both systems; check the current status before retrying.

How the pieces stay consistent

• One catalogue. The portal never holds a second product database you have to maintain; it receives a projection of the one you already keep.

• One stock ledger. Retail, POS and wholesale demand all resolve against the same quantities.

• One order vocabulary. A Shopify order, a Wolt order and a walk-in sale all end up describing themselves the same way, which is what makes reporting across them meaningful.

• Visible changes. Check the current status in each workspace after a cross-system change, and report a mismatch rather than retrying blindly.