Catalogue and procurement
In productionSupplier price files and APIs imported into a single catalogue with per-organisation overlay pricing, feeding quotes, purchase orders and the client storefront.
Measured: 275,656 catalogue products and 515 domain price points imported.
What it does
- Supplier feeds ingested on a schedule, each with its own field mapping rather than a generic guess.
- A shared global catalogue with a per-organisation overlay, so your pricing is yours.
- Product enrichment and image coverage, so a quote does not go out with blank rows.
- Purchase orders raised against the supplier the line was costed from.
- Stock and availability surfaced where a decision is made, not in a separate tab.
What it does not do
- SIX PURCHASE ORDERS in production. The catalogue underneath is heavily exercised; the PO workflow is not.
- Two suppliers need an outbound proxy because they block datacentre IPs, which is configuration you inherit.
- Feeds are Australian-focused. `organizations.region` gates which are offered.
What it replaces
- Distributor portals
- A pricing spreadsheet
Included in the single per-user price. No per-module or per-endpoint add-ons.
Read the guide
How this is actually set up and run, in the documentation.
What it connects to
Each of these has its own page, with how much production traffic it is carrying.
More in commercial
QuotingBuilt, lightly used
Quotes priced from live supplier cost, not last year’s list price.
Invoicing and paymentsIn production
Invoices to Xero, payment status back, direct debit collected nightly.
Agreements and renewalsBuilt, lightly used
What each client is contracted to, and what is about to expire.