Pricing

The tools that keep operations running.

Full import and export, a completeness report, Shipping Desk for picking and shipping, and control over the jobs running in the background. You can see what is happening, and you decide when it happens.

Import and export for the whole catalogue.

01 · Import & export

Import and export share one field catalogue, so a file you export can be read back in without remapping. Example view with invented data.

02 · Completeness report

Keep the products complete.

Every row hands off to bulk editing with the selection already made, so the gap can be filled in the same sitting. Example view with invented data.

Shipping Desk.

03 · Pick, pack and print inside the platform

Picking

Pick lists in batches

Gather the day's orders into pick waves by location, with a pick list for the whole wave.

Packing

Scan against the order line

Every scanned item is checked against the order, so a mispack is caught at the station rather than at the customer.

Shipping

Labels on the spot

The shipping label, packing note and return label print at the station, and the tracking number goes back to the order and the customer.

Example view with invented data.

The background jobs — visible and controllable.

04 · Queue, Cache and Index Manager

Queue Manager

Every queued job in one list: order sync, price calculation, feeds, mailings and imports. Pause a queue, reprioritise, run now or rerun what failed.

Shows
Queue depth, wait time, errors
Does
Pause · resume · run now · rerun

Cache Manager

See which cache layers are warm and when they were last filled. Clear a single surface — category pages, product pages, prices — instead of the whole store.

Shows
Hit rate, age, size
Does
Clear selected layer · warm up

Index Manager

Search and category indexes with status per index. Run a partial reindex of what changed, or rebuild from scratch when the attribute schema has been reworked.

Shows
Records, lag, last build
Does
Partial reindex · rebuild · pause

Example view with invented data.

Without visibility

How it looks otherwise

Nobody knows why a product is not showing in the store

Imports run from a script only one person understands

Cache is cleared by restarting the whole environment

Shipping happens in a separate system that does not know the order

With the tools

You are in control

The completeness report points at the exact field

Import templates can be run by anyone on the team

One cache surface clears without touching the rest

Picking, packing and shipping happen on the order itself

Questions about the tools.

Common questions

Which file formats does import handle?+

CSV, Excel, XML and JSON, from an uploaded file, FTP, a URL or the API. The mapping is saved as a template and can be scheduled.

Can we test an import before it saves?+

Yes. A dry run shows exactly which rows would be created, updated or skipped, without saving anything.

How is completeness defined?+

You set rules per channel: which fields are required for publishing, for a feed or for filtering. The report is scored against those rules.

Does Shipping Desk work with our carrier contracts?+

Yes, through the shipping integrations. Labels, packing notes and return labels print from the station and the tracking number goes to the customer.

What happens if we pause a queue?+

The jobs stay in the queue and run when it resumes. The store keeps working, but the paused step — a feed, say — does not update until the queue starts again.

What happens when we rebuild an index?+

The old index keeps answering until the new one is finished, and the switch happens once the build is verified.

Who is allowed to run these tools?+

Permissions are set per tool. A warehouse colleague can have Shipping Desk without reaching import or job handling.

See the tools in use

Bring a file and a day’s orders.

We run an import, show the completeness report on the result and pack an order in Shipping Desk.