Link your BOMs to Materials and Suppliers
You can now link BOM components to your Material Library and Supplier Management records directly through the BOM Integration API, using materialCustomId and orgCustomId.
You can now link BOM components to your Material Library and Supplier Management records directly through the BOM Integration API, using materialCustomId and orgCustomId.
You can now store confirmation and approval dates directly on purchase orders through the Purchase Order (V3) API, in addition to entering them manually on the UI or via PO file import.
You can now create, read, and replace critical quality points (CQPs) for Style, Item, and Material directly from your own systems, so you no longer need to enter or upload them through the UI.
You can now retrieve reason codes for aborted, waived, rejected, split, and reset inspections through the List Inspections and Get Inspection API endpoints.
You can now create, update, delete, list, and get taxonomy categories for style/item and material taxonomies through the Taxonomy Category APIs, so you no longer need to rely on CSV uploads or UI edits to keep your product classifications current.
You can now update the product list, including item, style, or material details, directly through the same Upload/Update Pre-Created Lab Test API you already use to send test data.
Once your CPSC eFiling data mapping is configured, you can call the Get CPSC eFiling Data API endpoint to retrieve structured, compliance-ready certificate data for one or more completed lab tests, formatted for whichever filing method you use: CPSC Product Registry, Reference PGA Message Set, or Full PGA Message Set.
The bill of materials (BOM) Create, List, Update, and Get API endpoints now accept and return two new fields, countryOfOrigin and attribute, allowing your integrations to programmatically capture where each component originates and what certification requirements apply at the material level.
Gain full visibility into your product, item, and material data with the new Get API integration, designed to return rich data aligned with upsert-items API.
The Purchase Order V3 APIs now support unit_cost_currency_code and total_cost_currency_code fields, enabling accurate cost tracking and reporting across both PO and Item levels.