Order Intake & Confirmation

High complexityOperations40–60 / day

Order Intake is Westvale's highest-volume workflow and the one where mistakes cost the most. A customer PO arrives by email, gets matched and entered in Odoo, is checked for stock and credit by hand, reconciled against a pricing spreadsheet, logged in a daily tracker, then confirmed and released to the warehouse. It spans three systems, leans entirely on one coordinator, and catches its exceptions late — which is why it scores 72 and is the first candidate for an operator deep-dive.

What this process involves

A new order email lands in the shared Gmail inbox. The order desk looks the customer up in Odoo to confirm they exist and check pricing tier and credit terms, verifies on-hand stock for each line, and — when an item is short or the order would push the customer over their credit limit — pauses to email the customer or route to Finance. The sales order is built in Odoo, line prices are cross-checked against the current Google Sheet price list and overridden by hand where Odoo is stale, the order is logged in the daily tracker, and finally the SO is confirmed and released to the warehouse with a confirmation email to the customer.

Complexity score breakdown

System fragmentation

Spans Gmail, Odoo, and Google Sheets with manual re-keying between all three.

Decision density

Stock check, credit check, and pricing reconciliation on every order.

Exception rate

Backorders, over-limit accounts, and price mismatches recur and branch the flow.

Single-owner dependency (SPOF)

One coordinator keys virtually all of it — no backup.

Source-of-truth conflict

The real current price list lives in a Sheet, not in Odoo.

Total72 / 100

Systems it touches

Gmail: shared inbox where customer POs arrive and confirmations are sent. Odoo: ERP of record for customers, inventory, and the sales order. Google Sheets: daily order tracker and the real, current price list.

GmailOdooGoogle Sheets

Risks and friction

Single point of failure — the order desk

Intake runs almost entirely through one coordinator. If Marcus is out, order entry effectively stops; the tacit pricing and exception knowledge isn't documented anywhere.

Exceptions caught late

Stock and credit checks are manual, so backorders and over-limit accounts are often discovered after the customer has already been promised — forcing awkward walk-backs.

Source-of-truth conflict on pricing

Odoo's prices are stale; the real price list lives in a Google Sheet, so every order is reconciled and overridden by hand — an undocumented workaround that is easy to get wrong.

Evidence links

scope boundary

1 claim · 1 evidence source

view

Starts at an order email in the shared Gmail inbox; ends when the Odoo sales order is confirmed and released to the warehouse.

ownership

1 claim · 1 evidence source

view

Order Desk (Marcus) accountable; Warehouse and Finance participate.

systems of record

1 claim · 1 evidence source

view

Gmail (intake), Odoo (ERP / sales order), Google Sheets (daily tracker + real price list).

frequency

1 claim · 1 evidence source

view

40–60 orders per day, every business day; Monday spikes.

single point of failure

1 claim · 1 evidence source

view

Order desk is a single-owner dependency — if Marcus is out, intake stops.

friction

1 claim · 1 evidence source

view

Manual stock and credit checks surface backorders and over-limit accounts late, after the customer is promised.

Ready to go deeper?

Add an operator capture to extract the L4 process map — every step, handoff, and exception backed by evidence.