Everything the platform does
Nine areas, 72 capabilities. Every one is built and running today. Nothing on this page is a roadmap item.
| 4 | apps | One for each job, not four tabs on one |
| 103 | screens | 9 storefront, 49 back office, 24 warehouse, 21 HQ |
| 17 | roles | Separate duties without custom work |
| 77 | permissions | Granted one at a time, never by job title |
| 22 | countries | Each with its region, currency and language |
| 8 | languages | Including Arabic, with the interface mirrored |
The storefront
Employees9 screens
Each employee sees a catalog built for them, from their department, location, job and group. Two people at the same company can open the same page and see different products.
- Per person catalog
- Employees see what their role, department and location allow. You choose per product whether the rest is hidden or shown with the reason.
- Points, not money
- Employees spend from a running balance of points. You choose what the points are called.
- Approval routing
- An order over an amount you set waits for a named manager before any stock is reserved.
- Order and period caps
- Caps are checked against live records at the moment of ordering, so two orders placed at once cannot both get through.
- Campaigns and seasons
- Schedule banners and collections to start and stop on set dates. Nothing to take down by hand.
- Search
- Keyword search across the whole catalog, with the closest match first.
- Favorites and saved cart
- Saved items stay saved, and a cart survives closing the tab.
- Order tracking
- Status from the moment the order is placed, not from the first carrier scan, so there is no silent gap while it is being picked.
- Eight languages
- Including Arabic, where the whole interface mirrors right to left rather than being translated in place.
Catalog
MerchandisersOne setup, every combination
Most catalog work is the same jacket in twelve sizes. Set it up once and every combination is created for you.
- Options and variants
- Add an option and its values, and every combination is generated with its own code, price and stock.
- Categories, tags, brands
- Reorganize categories without breaking the menus, banners and pages that point at them.
- Collections
- Hand picked groups of products for campaigns and featured sections.
- Media library
- Every image is checked on upload by its actual content, not its file name.
- Hero and gallery
- Order the photos, choose the main one, and reuse the same shot across products.
- Related products
- You choose what shows together, so a jacket suggests the gloves that match.
- Translations
- Names and descriptions per language, falling back to a default wherever one is missing.
- Bulk changes
- Publish, retire or hide many products at once, with the change recorded.
People and access
HR and IT17 roles, 77 permissions
Access is decided by what somebody is allowed to do, never by their job title. Adding a role is a configuration change, not a code change.
- Seventeen roles
- Across four areas, each with a rank. Nobody can grant a role at or above their own.
- Seventy seven permissions
- A screen and the action behind it check the same permission, so what somebody can see always matches what they may do.
- Groups and audiences
- Group people by a fixed list or by rules that re-evaluate as they change department or job.
- Org structure
- Department, job, location, region and country, each usable as a rule for who sees what.
- Invitations
- A time limited link lets a new employee set their own password, so no administrator ever types one.
- Credit grants
- Give an allowance to one person or a whole group, and every grant is recorded permanently.
- Store preview
- An administrator can view the storefront exactly as a named employee sees it, read only.
- Audit trail
- Every change records who made it, what changed, when and from where, in the same transaction as the change.
Inventory
OperationsAppend only
Stock is worked out from every receipt, pick and adjustment rather than kept as a single number, which is why two people cannot both claim the last unit.
- Movement ledger
- Every receipt, pick, adjustment and transfer is recorded permanently, and the count is always the sum of them.
- Bins and locations
- Which shelf a unit physically sits on, so a picker is sent to a place rather than to a search.
- Cycle counts
- Count part of the warehouse at a time, and any difference is recorded with a reason rather than corrected quietly.
- Transfers
- Stock moved between warehouses stays in transit until the receiving end confirms it arrived.
- Reorder policies
- A minimum and a reorder quantity per item, raising an alert before you run out.
- Adjustments and write offs
- Never a silent correction. Each one carries a reason and the person who made it.
- Availability states
- In stock, low, back orderable or unavailable, worked out from real stock rather than typed in.
Fulfillment
The warehouse24 screens
An outside warehouse gets its own portal to work from. It only ever sees the orders assigned to it, and nothing else in your account.
- Order routing
- Each order goes to the warehouse that has the stock, split across up to three when no single one can cover it.
- Pick waves
- Group orders into one batch to pick together. Anything short becomes a back order with the reason attached.
- Parcels and cartons
- Preset carton sizes, and order lines assigned to parcels with the right weight and dimensions.
- Rates and labels
- Compare carrier rates, buy the label, and void it when the wrong one was bought.
- Quality inspection
- Incoming goods are photographed and checked before they are approved for sale.
- Quarantine and returns
- Stock that fails inspection is held back and returned to the vendor rather than put on the shelf.
- Receiving
- Every delivery is checked against the purchase order, so receiving more than was ordered is flagged.
- Carrier accounts
- Each warehouse can hold its own carrier login and a default, with a way to test the connection works.
- Exceptions
- Shipping problems and stuck parcels arrive as work to do rather than as a line in a log.
Procurement
BuyersMulti vendor products
Most products come from more than one supplier: a jacket may need a shell from one vendor, a lining from another and an embroidery house for the logo. Each one is tracked against the finished product.
- Vendor records
- Addresses, contacts and what each vendor can actually make, and their portal credentials, which are stored encrypted and revealed only to somebody holding the permission, one at a time, with every reveal recorded.
- Supplier breakdown
- Which vendor supplies each part that goes into a finished product.
- Revisions
- Change how a product is made by copying the current version, editing it and activating it, with every earlier one kept.
- Purchase orders
- Raise, send, print and track them, with each line checked against what actually arrived.
- Replenishment
- The system proposes what to reorder from demand and your rules, and you approve before it becomes an order.
- Invoice matching
- A vendor invoice is checked against the order and the receipt before anyone pays it.
- Landed costs
- Freight and duty spread across the lines, so you see the true cost of a unit rather than its list price.
- Documents
- Contracts and certificates held against the vendor they belong to.
Finance
FinanceNo revenue to book
Nothing is sold to an employee, so there is no revenue to account for. The cost center that owns the order is charged internally at the end of the period.
- Cost centers
- Every order line carries a cost center, taken from the employee or set by an administrator.
- Chargebacks
- Raised at the end of the period, and reversed by a new entry rather than by deleting the first one.
- Periods
- Opened and closed deliberately, so a closed month stops changing.
- No rounding errors
- Money and credits are held as whole numbers, so a fraction is rejected rather than quietly rounded.
- Real cost, not list
- Budgets are charged what the item actually cost, freight and duty included.
- Reports
- Spend by cost center, by department and by period, read straight from the record.
Platform operations
The platform operator21 screens
The operator's own back office, used to run the business behind the platform. It is the only part that can see across clients, and no client can reach it.
- Client records
- Standing, health, suspension and notes that survive the account manager leaving.
- Licenses and entitlements
- Per feature and per client, so a plan is enforced rather than described.
- Plans
- Priced per seat per year and edited here, so what a client is quoted comes from this table rather than a rate card somebody keeps separately.
- New client setup
- A prospect becomes a live account with its own store, its administrator and its invitation.
- Invoices and payments
- Issued, voided and paid, with the overdue figure on the dashboard rather than in a report.
- Contracts
- Generated from versioned templates, sent, signed and voided, with the version recorded.
- Live security checks
- Twenty four checks run daily against the live database, reporting what is true now rather than last week.
Integration
Engineers19 endpoints
If your company already has an employee app, the store can live inside it. Your app says who the employee is and gets back the exact catalog that person can order from.
- Session handoff
- Your app tells us who the employee is. A new identifier creates the account, a known one resolves to the same person every time.
- Catalog endpoint
- The same catalog the web store shows, filtered to what that one person may order.
- Shared basket
- One basket per person. Add to it in your app, see it in the web store, and the other way round.
- Balance
- The points a person has left, and what lapses within thirty days, read from the ledger.
- Order placement
- Place the order in one call, from the shared basket or from a basket you hold.
- Order reads
- Status, lines and full history, for one order or for everything a person has ordered.
- Webhooks
- Every order event is pushed to you, carrying the employee identifier you gave us so you know who to tell.
- Retry and sweep
- A delivery that fails is retried on a schedule rather than lost.
- Scoped tokens
- Tokens limited to exactly what each one needs, revocable one at a time.
- Test delivery
- Send a real test event to your endpoint from the screen before you go live.
Capabilities listed72
Which of these would your first store actually use?
Book a walkthroughHalf an hour, one order walked the whole way through.