A wholesale reorder portal can let an existing customer request familiar products again without treating an old order as a new commercial commitment. Use Airtable to preserve the previous order, create a separate reorder request with new quantities, and let staff confirm current pricing and availability before accepting it.

Imagine fictional Fieldline Packaging supplying Harbor Shops with BOX-101 cartons and SLEEVE-202 sleeves. Harbor wants another delivery but needs fewer cartons this time. The useful outcome is a clear request based on known items, followed by a reviewed confirmation, not a one-click promise that last quarter’s price and stock still apply.

Separate the historical order from the new request

Proposed tables are Customers, Products, Previous orders, Previous order lines, Reorder requests and Reorder lines. Customers has Name as text and Email as email for the designated portal contact. Products has SKU and Product name as text, Current description as long text and Offered for reorder as a checkbox.

Previous orders has Order reference as text, Customer as a link and Order date as a date. Previous order lines links an order and product and stores Fulfilled quantity as a number and Historical unit price as currency. Keep historical values as records of that transaction, not live lookups that change when the catalog changes.

Reorder requests has Request reference as text, Customer and Source order as links, Desired delivery date as a date, Delivery instructions as long text and Review state as a single select. Reorder lines links the request, Customer and Product, with Requested quantity as a number, Requested notes as long text, Offered quantity as a number, Offered unit price as currency and Staff explanation as long text.

The separate Customer link on each displayed line supports a direct portal-user relationship. Staff, rather than the requester, maintains identity links, source-order links and commercial offer fields. This first version uses staff-prepared rows to avoid depending on an unverified automatic copy-order action.

Prepare a repeat-order worksheet

After receiving a reorder inquiry, staff checks that the source order belongs to the correct customer. Create a new request and fresh lines for the relevant products. Leave Requested quantity empty or explicitly ask the customer to review a proposed quantity; do not silently treat the previous fulfilled quantity as a fresh instruction.

Label prior quantities and prices as historical. For BOX-101, the previous delivery might have been 500 while the new request is 300. If SLEEVE-202 has been discontinued, explain that fact and keep any proposed replacement separate until the customer agrees. Do not relink the historical line to a different SKU.

Use the Users table setup to create the portal’s customer relationship. Add Reorder requests and Reorder lines through their direct Customer links. Expose the new quantity and request notes while keeping catalog ownership and staff decisions outside customer inputs.

Make customer access and editing deliberate

Configure a verified login using the email verification guide. Set each private view according to the personal-record filtering instructions. The shared catalog, if you show one, is a separate design decision; it must not reveal another customer’s order history or negotiated prices.

For the prepared-row approach, the customer edits existing lines rather than browsing all earlier order lines. Display SKU and current description for reference. If you later add product selection or line creation, inspect the linked-record creation controls and finder scope before launch. A filter on the top-level request does not by itself prove every nested picker is appropriately restricted.

Collect a requested delivery date and any changed delivery instructions. Ask staff to verify material changes through the usual account process. Do not put payment-card details, account credentials or sensitive shipping documents into this ordinary reorder form.

Confirm current terms before fulfillment

Staff reviews the complete parent request and each line, then records offered quantities and prices. A useful Review state sequence is Draft, Ready for review, Clarification needed, Offer prepared, Confirmed and Declined. These labels describe your operating process; choosing Confirmed does not collect payment or reserve inventory.

When only 200 cartons are available, retain Requested quantity 300 and record Offered quantity 200 with the reason. The customer should be able to distinguish what they asked for from what the supplier can provide. Record agreement through the team’s established confirmation process before sending the request into fulfillment.

If a customer changes a quantity after an offer was prepared, re-review the offer rather than assuming the earlier total still applies. Preserve the prior offer reference and add a new version or explanatory record when necessary. Tax, shipping, payment terms and inventory allocation belong in the appropriate commercial systems, not an inferred formula from an old invoice.

Keep history stable and test the exceptions

Once staff completes review, restrict the finished request in every available customer editing route. The history-view editing guide explains the view-level control and its limits. Keep the original order untouched throughout this process.

Test a changed quantity, a discontinued product, a price change and two customers with the same SKU. Confirm that creating the reorder changes no historical quantities, reserves no stock and sends no invoice. These are recommended checks rather than observed tests. The separate sample request workflow covers evaluation samples; this model focuses on repeat commercial requests that still need a current offer.