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.
What is in it
Import CSV, XLSX or REST feeds, map them to a schema and the AI matches requests against them.
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 end type, flutes, coating and diameter for one request line to the one product that fits it.
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.
It follows your products
Switch a product on and what it brings to this area appears here.
How Products follows the products a workspace switches on: Sales Engineer on its own, then each product that brings a view of its own (Source: Suppliers' prices), drawn by the platform's own switcher for each setup.
Source adds Suppliers' prices, for roles that see cost
Questions
- Product data lives in supplier files and spreadsheets, so matching a request means reading them by hand.
- 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.