- Overview
- API Resources
Supply Chain & Retail Solutions API guide
The Quote Pricing API resources support the Commercial Pricing solution, a B2B pricing application that enables businesses to manage quote-based pricing across customers, merchants, products, and regions.
For a full overview of the solution, see About the Commercial Pricing Solution.
Data model
The Quote Pricing data model centers on products, customers, merchants, and regions, linked through pricing records and quote lines that track the full quoting and sales lifecycle. See Data Model for the full entity relationship diagram and table summary.
Ingestion method per table
Commercial Pricing uses the historical state of customers, products, prices, and merchants as features in its pricing model — so most tables need their history preserved, not overwritten. The table below records the recommended operationType for each resource.
| Resource | Description | Operation |
|---|---|---|
| Competitor Prices | Competitor pricing data per product and region | APPEND |
| Customers | Customer records including category, subcategory, and price list assignments | APPEND |
| Data Model | Entity relationship diagram and table summary for the Quote Pricing data model | — |
| List Prices | Standard list prices per product, region, and price list | APPEND |
| Merchants | Merchant records including category and subcategory | APPEND |
| Product Costs | Cost of goods per product and region | APPEND |
| Products | Products available for quoting, including category and bespoke flags | APPEND |
| Projects | Project records used to group and track quote activity | APPEND |
| Quote Lines | Individual quote line items linking products, customers, merchants, and regions | UPSERT |
| Regions | Geographic regions used to segment pricing and cost data | APPEND |
| Sales | Completed sales transactions linked to quote lines | UPSERT |
The pattern follows the schema's primary keys. Tables with UPDATED_AT in the primary key — products, customers, regions, merchants, projects, list prices, competitor prices, and product costs — use APPEND, so each new version of a record is preserved as a distinct row. Quote lines and sales use UPSERT because re-submissions are usually corrections that should overwrite in place, not create duplicates.
If you are not sure which operation to use for a custom or non-listed table, look at the rolled-out schema's primary keys (fetch via GET /api/v2/schema?solutionName=…): a temporal column in the PK is the signal that APPEND is the intended operation. See Operation types for the underlying framework.