Platform area
The catalogue every quote is matched against
One catalogue of products described by schemas, filtered by their attributes and priced by rules.
The catalogue grid holding the first 6 of the 10 mm endmills in a cutting tool catalogue, with SKU, end type, flutes, coating, price, stock and lead time.
Why and how
- Why
- Product data lives in supplier files and spreadsheets, so matching a request means reading them by hand.
- How
- Import a CSV, XLSX or REST feed, map the columns to a schema, and the AI matches requests against it.
What is in it
Products
Search the grid and filter by any attribute the schema marks as a filter.
The catalogue filter rail over a 300 endmill file, narrowed by flute count and coating for one request line; the diameter it asks for is not in the list, so there is no exact product.
Schemas
Start from a preset schema, read one from a file or build your own.
The Cutting tools schema from the preset library: the product form its fields produce and the filters it adds to the catalogue grid.
Imports
Map columns, check the rows, import; REST feeds refresh nightly or on demand.
Pricing
Quantity breaks by product, category, schema or service, on every quote line.
Suppliers' prices
Every supplier's price for a product side by side, the best picked out.
The products that bring it
- Sales EngineerBrings itSchema based matching, with the fit score taken apart field by field and one of four decision bands
- WizardBrings itA wizard selects over the catalogue's own schema fields rather than a separate product list
- CommerceBrings itCommerce puts your catalogue online as a B2B trade site and connects it to the platform, and gives your customers their own sign in.
- SourceBrings itThe Suppliers' prices view: each product's best supplier price beside its own cost and default supplier
- StockBrings itStock keeps one true quantity for everything you hold, wherever it is.
The parts it hosts
- PricingQuantity breaks and special prices set once against a product, category, schema, design module or service, so a whole range prices together
- CostingA cost on every product, accepted from the best supplier price with its drift shown, and read by every quote line's margin
- IntegrationsCSV imports, a REST connection synced daily and the API's bulk product upsert, each able to keep a catalogue current
- DocumentsQuotes, orders, dockets, drawings, work orders, labels and attachments, templated and branded
- ActivityEvery action recorded, and the notifications the team and the org's customers receive
It follows your products
- AI
- Quotes
- Orders
- Customers
- Catalogue
- AI
- Sales
- Quotes
- Orders
- Customers
- Products
- Catalogue
- Stock
- Servicing
- Operations
- Route
Questions
- CSV and XLSX files through the import wizard, or a REST API feed refreshed daily or on demand. An interrupted import resumes where it stopped.
- No. The core fields load a working catalogue on their own; a schema from the library adds the attributes buyers filter on.
- No. Headings are matched to each field's name and synonyms by fixed rules, and you can change any mapping before the import runs.