Describe what you sell and how cancellations work. Makeform creates an order cancellation form with customer details, order number, reason, item selection, and requested outcome for review.
Route requests to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a prompt, adapt it, or send it to the builder.
Audience
Customers who want to cancel a product order
Format
Request form with item and reason selection
Prompt size
295 chars
Example form structure
Request form with item and reason selection
Customer name and checkout email
Order number and order date
Cancel the whole order or selected items?
Why are you cancelling?
Anything else we should know?
Suggested routing tags
New request
Needs review
Resolved
Ask for the order number and checkout email so staff can find the correct purchase.
Step 1
Identify
customer, order number, and purchase details
Step 2
Explain
reason, scope, and requested outcome
Step 3
Review
staff checks order status and store policy
Step 4
Respond
customer receives the next-step update
Why use a cancellation form
A structured order cancellation form gathers purchase details and customer intent in one submission.
Require the order number and checkout email, with an order date or postcode as a useful secondary match.
Collect item names, SKUs, and quantities only for partial cancellations.
Send each request to the right inbox with its reason and order details.
Built for different orders
Start with questions matching your fulfillment model, then edit reasons and routing.
Order lookup, shipment status, item selection, and common reasons.
Booking reference, service date, cancellation reason, and a branch for clients who would rather reschedule.
Purchase order references, affected line items, quantities, and a named buyer for follow-up.
Identify the specific shipment while keeping shipment cancellation separate from subscription-account changes.
Cancellation workflow
Turn your cancellation process into a focused form and connect submissions to reviewers.
Tell Makeform what you sell, which identifiers staff use, and what customers may cancel.
Add your cancellation reasons, item fields, contact details, and a plain explanation of what happens after the customer submits.
Show SKU and quantity questions for partial cancellations, or preferred dates when a service customer chooses rescheduling.
Publish the form link, place it in order emails or a help center, and send complete requests into the team's review channel.
Form vs email vs generic contact box
Structured fields reduce follow-up while leaving your team in control of the outcome.
Field guide
Identify the purchase, record the requested change, and set an expectation for review.
Customer
Collect enough information to locate the account. The checkout email is often more useful than a different contact address.
Order lookup
Require a clearly labeled order number. Add secondary details staff can compare if the number is mistyped.
Cancellation scope
Ask whether the customer means one item or everything, then reveal line-item fields only for partial requests.
Reason
A short reason list categorizes requests, while Other avoids forcing a wrong answer. Keep comments available for context.
Conditional paths
A partial cancellation needs item details; a service request may offer rescheduling; a shipped order may need another path.
Expectation
Say the team received a request and will review it. Do not claim cancellation before the change is processed.
Related tools
Pair cancellation intake with ordering, returns, complaints, and account-level cancellation forms.
Collect return or exchange details after an order has arrived.
Open toolGather product options and special instructions for customized purchases.
Open toolHandle account-level membership cancellation separately from a single order.
Open toolCollect customer, product, quantity, and delivery information online.
Open toolFAQ
Practical answers for e-commerce teams, service businesses, and customers requesting an order change.
It is a structured way to ask a business to stop all or part of an order. It records contact details, order number, affected items, reason, and requested outcome for staff review.
Collect customer name, checkout email, order number, and date. Ask whether to cancel the full order or selected items, gather relevant item details, offer reasons plus Other, and allow comments. For services, add the appointment and rescheduling preference.
Not by itself. The form collects and routes a request. Staff or a connected workflow must review the order and act. Say request received unless a separate, verified process completes the cancellation.
Yes. Ask whole order or selected items, then show product, SKU, variant, and quantity fields for partial cancellations. Reviewers receive an exact list without burdening every customer.
Yes. Use the service, booking number, date, and time instead of product fields. Ask whether the client wants to cancel or reschedule, then show preferred dates when relevant.
Yes. Makeform provides unlimited free forms and responses, so you can generate, edit, publish, and collect cancellation requests without a response cap. A paid tier is available to remove the Makeform badge.
Link it from confirmation emails, shipment pages, your help center, and support replies. Reuse one URL so the team receives a consistent record.
Confirm receipt, explain the next step, and provide a support route. Do not say the order is cancelled unless your workflow completed the change. Distinguish a submitted request from a finished cancellation.
Replace cancellation email threads with complete requests.
