Documentation

Getting started

Create an account, pick a plan, and the 14-day trial starts without a card. The first three things worth doing, in this order:

• Connect one channel - the one with the best catalogue.
• Import it and let the products, variants and images land.
• Connect the second channel, which is where the product starts being worth having: one stock figure, two shops.

Invite the rest of the team from Settings. Everybody gets a role, and a role is a set of permissions rather than a job title we assumed.

Connecting a channel

Six channels, two ways in.

Channel	How it connects
Shopify	Install from the store, or paste an Admin API access token
eBay	Sign in at eBay and approve the application
WooCommerce	A REST key pair from the WordPress admin
Magento	An integration token from the Magento admin
Amazon	Not available yet - awaiting approval of our developer registration
TikTok Shop	Not available yet

A connection is verified the moment it is made: we call the channel, read the shop back, and only then is it saved. A store that cannot be reached is never shown as connected.

Every connection can be paused. A paused channel is still connected and still visible; nothing is sent to it until it is resumed, which is what you want during a stocktake or a price rework.

The catalogue

One product record, whatever the channels call it. Variants and options survive the trip, images keep their order, and the SKU is the thing everything else hangs from.

• Types and tags organise the catalogue. Renaming a type merges it, which is how a catalogue imported from three shops stops having three words for the same thing.
• Condition is a first-class field, because a marketplace asks for it and a shop does not.
• Safety and compliance details for the EU are held on the product: the responsible person, the warnings, the pictograms. They are picked from the channel's own list rather than typed as free text, so what is sent is what the channel accepts.
• Images belong to the product and to the channel that has them, so re-importing a shop does not multiply the same photograph.

The list works at half a million SKUs: search, filter, sort and paginate are all answered by the database rather than by loading the catalogue into a browser.

Categories and mapping

Your categories are yours. Each channel then gets a mapping, and the shape of that mapping depends on the channel:

• A shop - Shopify, WooCommerce, Magento - has a taxonomy the merchant owns, so a category of yours is created there.
• A marketplace - eBay, Amazon, TikTok Shop - has a fixed taxonomy, so yours is resolved to one of their leaves. That leaf then dictates which item specifics are required, and the product screen asks for exactly those.

Marketplace taxonomies are asked for live rather than cached. A stored copy goes stale silently and the bill arrives months later at publish time.

Publishing and listings

A product goes to a channel from the product itself or in bulk from the list. The preflight runs first and tells you what is missing before anything leaves: a required aspect with no value, a category not mapped, a picture the channel will refuse.

After that, edits look after themselves. Every change marks the listing, and a sweep drains the marked ones every couple of minutes. The merchant is not the scheduler: nobody has to press "send" after fixing a price.

Stock

One stock position across every channel, so the same unit is not sold twice. Orders reserve, fulfilments consume, and the number every shop sees is derived rather than typed.

• Stock rules per connection. Send everything, hold a buffer back, cap what a channel is told, or share a fixed slice. A marketplace that punishes an oversell can be given less than a shop that does not.
• Every push is recorded with what was sent and what the channel answered, so a disagreement has evidence rather than opinions.

Warehouses and bins

Stock lives in a warehouse, and a warehouse has locations inside it: an aisle, a bay, a shelf, in whatever words the building already uses. A pick list is ordered by them, so the walk is short and the same every time.

Warehouses are archived rather than deleted. A ledger has to keep adding up, and the history of what was where is part of it.

Orders

Every channel's orders in one book, with the channel's own reference kept beside ours so a customer service call can be answered in either language.

• Lines resolve to your products by SKU, and what does not resolve is shown rather than dropped.
• Allocation reserves stock as an order arrives, oldest first.
• Money is kept in the currency it was taken in, with the conversion recorded.
• Addresses arrive as the channel holds them and are used for the label unchanged.

Picking and packing

A pick list is built from orders that can be filled, in bin order, and printed as a pick sheet. At the bench, each line is confirmed and the parcel is closed with a packing slip.

What was picked and packed is reported back to the channel with its tracking number, so the customer's shop account says shipped without anybody logging into it.

Shipping and documents

Packing slips and pick sheets are produced as PDFs, on the spot, from the same data the screen shows. Labels come from the merchant's own carrier account, which keeps the rates the merchant negotiated rather than an aggregator's markup.

Returns

A return starts from the order it came from. What comes back is inspected, restocked or written off, and the stock figure moves with the decision. The channel is told, and the reason stays on the order for whoever asks later.

Automation

Rules that watch what happens and act: pause a channel when a sync keeps failing, flag an order that cannot be filled, hold back stock on a line that is selling faster than it is arriving. Each rule says what it did and when, so an automation is something you can audit rather than a black box.

Analytics

What sold, where, at what margin. Cost lands from purchasing, fees land from the channel, and the profit line is what is left rather than a guess made from the price. Slow movers, out-of-stock losses and the channels quietly costing more than they return all have a number.

Purchasing and replenishment

Suppliers, purchase orders and what is on its way. Replenishment reads the rate of sale and the lead time and says what to order and when, and a receipt against a purchase order puts the stock and the unit cost in at the same time.

People and roles

Eight roles out of the box, from owner to warehouse operator, each a set of permissions rather than a label. A person who may pick a parcel does not have to be a person who may see a customer's telephone number.

Everything anybody changes is written to an audit trail with the person, the time and what changed. Every read of a customer's personal data is recorded too - see the privacy page.

Plans and billing

Plans differ by how many channels, products, orders a month and people they carry. The limits are shown in the product as they are approached, and hitting one is a prompt to change plan. Billing is Stripe's hosted checkout and portal, so card details never touch us.

The assistant

A help sidebar that knows the product and the state of your account. It explains why a listing is not going out, drafts a title or a description, and points at the screen that fixes the thing you are asking about.

It is never sent customer personal data. It works on products, channels and readiness, which is a property of what the code sends rather than a promise about a prompt.

When a sync goes wrong

Channels refuse things. The interesting question is always what was sent, what came back, and what to do about it, so that is what a failed sync shows: the channel's own words, the record it was about, and the action that clears it.

Nothing retries forever in silence. Work that keeps failing is set aside where it can be looked at, and a connection that has stopped working says so on its own card instead of being discovered at the end of a bad week.

Security and data

Hosted in London on Google Cloud, one organisation's data unreachable from another's session, channel credentials sealed with a key the database does not hold. The privacy page is the long version, including what is recorded about who looked at what, and for how long.