Working the quote board

Run it with your quote offer's id. Stage picks what you are working:

• pricing — requests waiting on YOU. The Price it action is the next step.
• awaiting_payment — priced and sent; the customer has the link and has not paid yet.
• paid — the payment landed and the order is through.
• all — everything against this offer, newest first.

Where each column comes from

Two sources, and the split is deliberate.

The seller order store answers Reference, Stage, Total, and Currency. It is the only authority on any of them. Nothing on this board second-guesses it, and the pack keeps no copy of a figure or a phase that could disagree with it.

⚠ It is read fresh on every run. An order read is otherwise served from a cache for up to a minute, and a board opened straight after pricing showed the request as still waiting on your price.

The pack's request records answer For (what the customer asked for, in their words), To (who to address it to), and Quoted as (the line you named the job when you priced it). The board plucks the submission references off the page it is about to show and fetches exactly those records in one bounded local read — no per-row read, no provider call.

⚠ None of it can come from Stripe. The checkout session carries a subject as price_data.product_data.description, but a pricing-phase order has no session yet — the session is created after you price it — and pricing is exactly the queue those columns matter for.

⚠ Rows opened before this pack gained Records storage show blank text columns. There is no row to read for them. The reference columns still identify them, and pricing one works normally.

⚠ The board reads orders, not the intake forms, so a request only appears once Open a quote request — or Open a quote request by hand — has run for it. If an accepted response has no row here, that recipe has not fired for it yet. Requests on record in the card counts the pack's own rows for this offer, so a number well above the listed orders is the sign of exactly that gap.

⚠ A page is at most 100 rows. The request records for a page are fetched with an exact in over its submission references, and that predicate admits 100 values — so the ceiling is the join's, not a display preference. Narrow with Stage rather than raising the limit.

⚠ An order stuck in awaiting_payment after the link expired cannot be re-quoted — order.quote only accepts a draft or pricing order. Cancel it and take a fresh request.