Give every customer a digital way to buy from you.
Products / SPICE Trade™
SPICE Trade™
SPICE Trade™ provides account-aware web and mobile ordering, status and collaboration for dealers, distributors and other non-EDI customers.
SPICE Trade™ customer storefront
In SPICE Trade™, a customer without EDI shops an account-specific catalog at its contracted prices, adds items to an order and places it, then follows the order from creation to confirmation, shipment and invoice in the same place. The products, prices and order shown are illustrative.
Contracted catalog
- Stainless steel ball valvePart # BV-10011" FNPT, 316 stainless steel $48.20/ each
- Industrial filter cartridgePart # FC-20035 micron, 10" $12.75/ each
- Industrial hose assemblyPart # HA-31003/4" x 50 ft, pressure rated $89.40/ each
- Carbon steel flangePart # FL-40052" 150# RF $21.10/ each
Your order (3)
- Stainless steel ball valveQty: 2$96.40
- Industrial filter cartridgeQty: 5$63.75
- Carbon steel flangeQty: 2$42.20
Estimated total$202.35
Create order
The problem
Manufacturers often run EDI customers through one channel and smaller buyers through phone, email or a separate commerce stack.
SPICE Trade™ is built for upper-mid-market and large manufacturers, industrial suppliers, CPG brands and distributors with established B2B infrastructure.
What it does
- Account-specific catalog and pricing
- Order entry and history
- Shipment and invoice status
- Roles and account hierarchies
- Responsive B2B experience
- Reuse of established O2C rules
How SPICE Trade™ works
- Browse The customer account determines the catalog, contracted prices and available locations.
- Order The buyer reviews order lines and delivery location, then submits order SO 20861.
- Confirm The existing enterprise O2C integration validates and returns the order confirmation.
- Fulfill ERP and fulfillment systems execute the order; shipment and logistics events return through the shared integration.
- Track The buyer sees order history, shipment progress and invoice presentment in one account experience.
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. Serve non-EDI customers through the same O2C backbone as EDI customers and reduce repeated order entry.
For the trading partner: a clearer way to participate. Browse contracted products and pricing, order conveniently and see fulfillment and invoice status.
Why this approach
Address the process around the technology. A separate storefront creates another downstream integration program. SPICE Trade™ extends your established EDI/API architecture and enterprise rules where practical.
Its role in the SPICE™ platform
The non-EDI customer channel. It reuses proven O2C integrations rather than creating a disconnected digital channel.
Extend your existing EDI/B2B architecture. Your established integration backbone can remain in place.
The SPICE™ platform
Where SPICE Trade™ 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 Trade™ for?
Upper-mid-market and large manufacturers, industrial suppliers, CPG brands and distributors with established B2B infrastructure.
How does it connect to our existing systems?
The solution is designed around supported enterprise interfaces and the transaction scope. SPICE Trade™ reuses your established order-to-cash integrations, and SPICE™ native middleware provides transformation: it 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 built into SPICE Trade™; it isn't a separate purchase. Embedded SpicY™ assistance is available in applicable SPICE Trade™ workflows for status, explanation, reporting and defined work. Its scope and controls are confirmed in solution design.
Talk to a platform specialist
Give your non-EDI customers a digital way to order
Bring your customer channels and the order-to-cash integrations you already run, and see SPICE Trade™ in your operating model.