Prepare a draft store order from a B2B customer email

Why use this

1. A merchant can receive a clear-looking B2B order that uses customer shorthand, pack quantities and informal product descriptions. Translating it directly into store line items risks quoting the wrong variant or quantity.

2. A draft-order review sheet could expose those mappings before the merchant commits to a quote. The useful output is a traceable interpretation of the request, including anything that still needs clarification.

Why an agent / simpler alternative

Useful judgment

Resolve product wording against a bounded catalogue and recognize ambiguous units or variants.

Simpler alternative

Use an order form or CSV import when customers already supply valid SKUs and unit quantities.

Unsuitable when

Negotiated pricing or unavailable variants require assumptions.

Proposed inputs

1. Name

   Customer order email

   Owner

   Merchant

   Minimum scope

   One verified customer request and relevant prior clarification

   Quality check

   Confirm requested quantities and recipient identity.

2. Name

   Catalogue and quote rules

   Owner

   Store owner

   Minimum scope

   Relevant SKUs, variants, pack sizes and approved pricing rules

   Quality check

   Check current availability and unit definitions.

Access and setup — proposed or unknown

Proposed minimum

1. Read-only email and catalogue snapshots; offline line-item preview first.

Compatibility unknowns

1. Unknown: exact runtime, store connector, tax fields and draft-order permissions.

External actions requiring approval

1. Writing a store draft, changing customer records or sending a quote.

Expected deliverable and review checks

Proposed artifact

Line-item mapping and draft-order preview with unresolved questions.

Critical checks

1. Every quantity has an explicit selling unit.

2. Variant, price basis, tax treatment and customer destination are reviewable.

Missing output evidence

No inspected draft order, quoted total or successful transaction is established here.

Failure signals and proposed responses

1. Signal

   “Two cases” becomes two individual items.

   Why it matters

   The quote may materially understate the request.

   Proposed response

   Show pack conversion and hold the ambiguous line.

2. Signal

   Customer shorthand matches multiple variants.

   Why it matters

   A plausible SKU can still be the wrong product.

   Proposed response

   List candidates and request clarification before drafting that line.

Effort and cost — unknown

Setup work

1. Map customer vocabulary and catalogue units.

Ongoing review

1. Check quantities, price rules and recipient before quoting.

Unknowns

1. Unknown: store access cost, tax configuration and catalogue cleanup effort.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

A fictional email orders “two cases of blue refill”; the catalogue has two blue variants with different pack sizes.

Acceptance checks

1. No single variant or total is asserted.

2. Clarification names both variant and pack-size ambiguity.

Stop conditions

1. A missing price, tax rule or product choice must be guessed.

Limits

1. Editorial preview proposal; no store state has been changed or quote sent.