Customer details
Know who to update.
Collect a name, usable contact route, and preferred channel for item-specific updates.
- Customer or company name.
- Email or phone number.
- Notification preference and consent.
Describe your unavailable products and fulfillment choices. Makeform creates a backorder form for the item, variant, quantity, customer contact, and preferred next step.
Route backorder requests to email, Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a stock workflow, edit its details, and send it to the Makeform builder.
Audience
Shoppers waiting for a sold-out retail product
Format
Short signup with variant selection and contact consent
Prompt size
220 chars
Example form structure
Short signup with variant selection and contact consent
Name and contact details
Which size and color do you need?
Requested quantity
How should we notify you?
Consent to receive a restock update
Suggested routing tags
Notify only
Order request
Staff review
Ask for the exact size, color, model, or SKU. A product name alone may not tell staff which unavailable variant the customer expects.
Step 1
Request
customer selects the exact unavailable item
Step 2
Review
staff checks incoming stock and customer details
Step 3
Confirm
customer receives availability and next steps
Step 4
Fulfill
pickup or shipping is arranged separately
Why use a backorder form
A structured backorder form records the item, variant, quantity, and requested outcome together.
Use variant dropdowns and a SKU field so staff can distinguish demand without decoding vague notes.
Ask whether the customer only wants a restock notification or wants staff to review an order request. Conditional follow-up fields keep each path short and relevant.
Notify inventory or sales and organize responses by SKU, quantity, and contact preference.
Built around real stock scenarios
Start with the workflow closest to your store, then replace the sample products, choices, messages, and routing rules.
Collect only the product variant, contact destination, and consent needed for a focused availability update.
Gather fulfillment preferences and clearly explain that staff must confirm inventory, timing, price, and the next ordering step.
Capture buyer details, multiple lines, target dates, substitutes, and split-shipment preferences for a purchasing conversation.
Record needed-by dates and alternate-item interest when an incoming shipment may be smaller than customer demand.
Build your workflow
Describe the products, customer path, and team responsible for each response.
List products and variants or explain how customers should enter a SKU and needed-by date.
Require product, quantity, and contact fields. Distinguish a request from a confirmed reservation or purchase.
Use conditional questions for notify-only, pickup, shipping, substitute, wholesale, or allocation paths so shoppers only see fields that apply.
Publish the form, notify the responsible team, and review submissions by SKU and quantity.
Form vs email vs product alert
The best method depends on whether you need a simple alert signup, a staff-reviewed order request, or purchasing details for several products.
Field guide
These six sections keep unavailable-item requests specific without implying confirmation.
Customer details
Collect a name, usable contact route, and preferred channel for item-specific updates.
Product identity
Use structured choices, or request the product name plus SKU, model, or product link.
Quantity and timing
Capture quantity and a needed-by date so staff can prioritize demand.
Request intent
Branch the form for customers who want an alert, staff review, or an alternative.
Fulfillment and substitutes
Ask about pickup, shipping, substitutions, and split fulfillment before staff responds.
Expectation message
State whether submission joins a notification list or starts staff review.
Related tools
Use related Makeform tools for simple availability alerts, pre-orders, general product orders, waitlists, and inventory changes.
Collect contact details and variant preferences when the only next step is a restock message.
Open toolGather product selections and customer information for items offered before their release or arrival.
Open toolCreate a general ordering flow for products that are currently available for purchase.
Open toolOrganize interest in a product, service, or allocation when access opens in stages.
Open toolRecord stock corrections that can change what staff see as available for customer requests.
Open toolCapture account, product, quantity, and delivery details for business buyers placing available-stock orders.
Open toolFAQ
Practical answers for retailers organizing requests for products that are temporarily unavailable.
A backorder form records interest in an unavailable item: product, variant, quantity, customer contact, and whether the customer wants an alert, order review, or substitute.
Include customer contact, product and SKU, variant, quantity, and desired next step. Add timing, fulfillment, substitute, and partial-quantity choices when relevant.
Not necessarily. If staff must check stock, timing, price, payment, or delivery, label submission as a request for review and confirm details separately.
Yes. Separate notify-only customers from order requests. Ask the first group for variant, contact, and consent; ask the second about quantity, fulfillment, and substitutes.
Yes. Use dropdowns for a small catalog or request a SKU, model, or product link. Wholesale customers can list several SKUs and quantities.
Show only dates your team is prepared to communicate, distinguish estimates from confirmations, and ask when the customer no longer needs the item.
Yes. Makeform provides unlimited free forms and responses. Generate, edit, publish, and collect requests for free; the paid tier removes the Makeform badge.
Send them to operations, sales, or purchasing. Notifications surface new requests, while a connected sheet can group demand by SKU, variant, quantity, and status.
Keep unavailable-item requests out of scattered inboxes.