Collect complete product data and move it into the systems that need it.
Products / SPICE Catalog™
SPICE Catalog™
SPICE Catalog™ gives suppliers a governed way to submit product information and gives the enterprise a structured process to validate, enrich, approve and synchronize it, and to keep it current as item data changes.
How a new item moves through SPICE Catalog™
A supplier submits a new item in SPICE Catalog™. Its required attributes, formats and business rules are validated, questions are resolved with the supplier in context, merchandising approves the record, and the complete product data is synchronized to your ERP, e-commerce platform and other downstream systems. The item shown is illustrative.
1Supplier submission
New item submission
Product name *Whole black pepper Description *Premium whole black peppercorns sourced from trusted farms. Category *Spices Pack size *12 oz Product images *
2Validate
Required attributes
- Product name
- Description
- Category
- Pack size
- Product images
- Regulatory information
Formats
- Text fields
- Numeric fields
- Date format
- Image requirements
Business rules
- Valid category
- Allowed pack sizes
- Unique item check
- Required compliance data
3Collaborate
- DSData specialistCan you confirm the country of origin for this product?
- SUSupplierYes, the country of origin is Indonesia.
- DSData specialistDo you have allergen information available?
- SUSupplierThis product does not contain any allergens.
4Approve
New item review
Whole black pepper
- Category
- Spices
- Pack size
- 12 oz
- Origin
- Indonesia
- All required attributes complete
- Formats valid
- Business rules passed
- Questions resolved
5Synchronize
SPICE Catalog™
Whole black pepperApproved
- Category
- Spices
- Pack size
- 12 oz
- Origin
- Indonesia
- Description
- Premium whole black peppercorns sourced from trusted farms.
The problem
Disconnected templates and repeated data requests slow item setup and leave internal teams chasing missing attributes.
SPICE Catalog™ is built for item setup, merchandising and product data teams working with supplier-submitted content.
What it does
- Supplier item-submission portal
- Configurable attributes and rules
- Review and approval workflow
- Spreadsheet and structured imports
- ERP, PIM and commerce mapping
- Shared status visibility
How SPICE Catalog™ works
- Submit The enterprise defines the category requirements. A supplier submits item SKU 4018 through the portal or a supported spreadsheet.
- Validate SPICE Catalog™ checks required attributes and category rules. A missing packaging attribute keeps the item out of the ERP.
- Correct The supplier receives clear feedback and corrects the missing packaging attribute in the submission.
- Approve The assigned enterprise reviewer approves the complete item under the configured workflow.
- Synchronize SPICE™ native middleware maps the approved content to ERP, PIM and commerce destinations; status remains visible.
An explanation of the workflow using representative data; implementation reflects the enterprise rules and integration scope.
For the enterprise and the trading partner
For the enterprise: more consistent execution. Reduce repeated data requests and manual preparation; improve product completeness before synchronization.
For the trading partner: a clearer way to participate. Receive clear category requirements, actionable corrections and visible approval status.
Why this approach
Address the process around the technology. DIY templates scatter versions and corrections. A data pool distributes standard content; SPICE Catalog™ also supports the enterprise-specific submission, validation and approval process.
Its role in the SPICE™ platform
SPICE Catalog™ supplies governed product content to SPICE Trade™ and other commerce experiences, with SPICE™ native middleware integration and SPICE Insight™ visibility and exception management.
The SPICE™ platform
Where SPICE Catalog™ fits
The highlighted parts run this process. Every other part runs on the same platform. Select any part to explore it.
Your ERPWMS · TMS · OMS stay the system of record
FAQ
Frequently asked questions
Who is SPICE Catalog™ for?
Item setup, merchandising and product data teams working with supplier-submitted content.
How does it connect to our existing systems?
The solution is designed around supported enterprise interfaces and the transaction scope. SPICE™ native middleware maps approved content to your ERP, PIM and commerce destinations, and translates X12, EDIFACT, IDoc and JSON, so trading partners don't change format. SPICE Connect™ can provide connectivity and operational ownership. Your ERP stays the system of record.
Can we start with one process or trading partner group?
Yes. Scope a priority process or trading partner group first, then extend the relevant shared integration, visibility and support services as requirements change.
How long does implementation take?
Timing depends on interfaces, document scope, business rules, deployment needs and trading partner readiness. SPICE™ establishes a rollout plan after discovery; there is no universal go-live promise.
Where does SpicY™ fit?
SpicY™ is not part of SPICE Catalog™ today. It works inside SPICE Insight™, SPICE Web OMS™, SPICE Trade™, SPICE iKompli™ and SPICE Digital Document Service™.
Talk to a platform specialist
Govern new-item setup from submission to synchronization
Bring your category requirements and the systems your item data feeds, and see SPICE Catalog™ in your operating model.