Accept, decline & conditions
How a vendor responds to an assignment — accept, counter on fee or due date, or decline — and what each path does.
After assignment, the Vendor reviews the order and responds. There are three outcomes, each driving a different status.
The three responses
| Response | Resulting status | What it means |
|---|---|---|
| Accept | Order Accepted3 | The vendor confirms as-is |
| Accept with conditions | Accepted with Conditions4 | The vendor counters on fee or due date |
| Decline | Order Declined2 | The vendor passes; order is reassigned |
Each response is driven through the order status endpoint:
Accept
The simplest path. The vendor accepts the order as assigned and it moves to Order Accepted3, ready for scheduling.
Accept with conditions
A vendor can counter-offer instead of accepting outright — for example, proposing a different fee or a later due date. The order moves to Accepted with Conditions4 with the vendor's proposed terms and notes attached.
The client then responds to the counter:
- Accept the conditions — the order proceeds with the agreed fee/due date.
- Counter again — the client proposes its own fee/due date.
Accept-with-conditions is a back-and-forth between vendor and client until both agree. The agreed conditional fee and due date are recorded on the order and carried into invoicing.
Decline
A vendor can decline with a reason (for example, out of coverage area, too busy, or other). The order:
- is marked declined (Order Declined2),
- returns to Order Unassigned16 for reassignment, and
- increments the reassignment count.
A decline isn't a dead end — it routes the order back for a new vendor. Capture the decline reason so operations can spot patterns (a vendor who always declines a region, a product no one will take) before it hurts turn time.
What's next
An accepted order moves into the work phase, starting with scheduling the property inspection.