A Work Order (in Unimarket) acts as an umbrella document. That ties together Purchase Orders and Invoices under a single Work Order number. It's designed for tracking estimated vs. actual costs across multiple related transactions (common in construction, facilities, or project-based procurement).

Work Orders are an integration-driven feature (created via an inbound web service message from an external system); rather than something manually created/manged in the Unimarket UI.

How They're Created

Via Inbound Integration (The primary method)

• Unimarket receives a uXML-formatted "Work Order" request message from the customer's external system (e.g., their ERP or project management system).
• This message creates the Work Order record inside Unimarket.
• Once created, the Work Order number is then referenced in two other integrations:
  • Community Order: When a Purchase Order is created, the purchase order can be linked to the work order on the Checkout screen.
  • Invoice: When invoices are processed, they can also carry the Work Order number, so all related costs roll up under that one Work Order.

Why It's Set Up This Way

This allows the customer's external system to track the full financial picture of a project or job (estimated costs vs. actual costs). By linking every PO and invoice back to a single Work Order; rather than needing to view each PO and invoice separately.

Troubleshooting

• If the customer has Work Order Integration and a buyer is unable to link a work order to a transaction. Community Administrators should reach out to the Unimarket Support team, for further assistance.