Bring every supplier into the same procure-to-pay process.
Products / SPICE Web OMS™
SPICE Web OMS™
SPICE Web OMS™ gives non-EDI suppliers a guided web and mobile experience for orders, acknowledgments, changes, shipments and invoices.
SPICE Web OMS™ supplier workspace
In SPICE Web OMS™, a supplier without EDI sees its open purchase orders, documents, alerts and exceptions in one workspace. It follows each order through its lifecycle, from purchase order received to acknowledgment, advance ship notice, invoice and payment, and acknowledges orders, creates ASNs and submits invoices from the order itself. The orders shown are illustrative.
Supplier workspace
Collaborate, fulfill and get paid through a single, governed process.
Orders12 4Requiring action
Documents8 2Pending
Alerts3 1Needs attention
Exceptions2 1Requires resolution
Order lifecycle
Recent orders
View all ordersThe problem
The long tail of suppliers often works through email, PDFs and spreadsheets, creating manual re-entry, chasing and late exceptions.
SPICE Web OMS™ is built for procurement, vendor compliance, supply chain and AP teams with non-EDI suppliers.
What it does
- PO delivery and acknowledgment
- Governed line-level changes
- Shipment and ASN creation
- Invoice creation with context
- Business-rule validation
- Role-based web and mobile access
- Fulfillment workbench for ERP/WMS workflow gaps
- Transportation and warehouse collaboration
How SPICE Web OMS™ works
- Receive PO The ERP issues PO 10482. The supplier sees required lines, quantities and dates in SPICE Web OMS™.
- Confirm Confirm 100 units for the requested date; required fields and quantities are checked.
- Manage changes Propose a line-level date change with a reason. The configured buyer workflow governs approval before an ERP update.
- Ship Create the ASN with order context, packing or handling units and labels where required.
- Invoice Create the invoice against the order and shipment; validation keeps related quantities and references consistent.
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. Get earlier confirmations, governed changes and cleaner shipment and invoice data without parallel manual processes.
For the trading partner: a clearer way to participate. See the order, outstanding tasks and validation feedback in a guided web or mobile experience.
Why this approach
Address the process around the technology. A basic web EDI form digitizes a document. SPICE Web OMS™ governs the supplier process, including order changes, shipment dependencies, invoices and claims or deductions where configured.
Its role in the SPICE™ platform
The non-EDI supplier channel. It reuses SPICE Connect™ and SPICE™ native middleware integration, with SPICE Insight™ visibility and exception management. SPICE Web OMS™ can also provide an order-fulfillment workbench for sales and distribution, and guided workflows for non-EDI carriers and contract warehouses.
The SPICE™ platform
Where SPICE Web OMS™ 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 Web OMS™ for?
Procurement, vendor compliance, supply chain and AP teams with non-EDI suppliers.
How does it connect to our existing systems?
The solution is designed around supported enterprise interfaces and the transaction scope. 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 Web OMS™; it isn't a separate purchase. Embedded SpicY™ assistance is available in applicable SPICE Web OMS™ workflows for status, explanation, reporting and defined work. Its scope and controls are confirmed in solution design.
Talk to a platform specialist
Bring your non-EDI suppliers into one governed procure-to-pay process
Bring your supplier mix and the confirmations, changes, ASNs and invoices you need from them, and see SPICE Web OMS™ in your operating model.