Describe how your team sends parcels, freight, documents, samples, or customer orders. Makeform turns the details into a practical shipping request form that collects sender and recipient addresses, item and package information, requested delivery dates, service preferences, billing codes, and handling instructions before a shipment reaches the logistics queue.
Route shipping requests to email, Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a complete prompt, adapt the operational details, or send it to the Makeform builder. The structures below show useful starting points rather than live generated results.
Audience
Employees asking an office or mailroom to send a package
Format
Request form with cost center and approval routing
Prompt size
549 chars
Example form structure
Request form with cost center and approval routing
Requester, department, and cost center
Recipient and complete delivery address
Package dimensions and weight
Pickup-ready and required arrival dates
Is this shipment international?
Suggested routing tags
Ready to quote
Address review
Scheduled shipments
Collect the requested arrival date separately from the pickup-ready date. Logistics can then choose a service level based on the real transit window.
Step 1
Request
addresses, contents, dates, and owner
Step 2
Review
missing data, restrictions, and budget
Step 3
Book
package, carrier, and service selected
Step 4
Track
reference shared and delivery followed
Why structured shipping intake
A message that says send this tomorrow leaves logistics chasing the street address, package weight, deadline, and budget owner. A structured shipping request form gathers the booking inputs together before work enters the queue.
Required address, contact, package, and timing fields turn a vague request into a shipment the mailroom or warehouse can assess without a chain of follow-up messages.
Conditional paths can reveal customs details for international parcels, dock access for freight, or damage photos for returns while keeping ordinary domestic requests short.
Each submission creates one request record with its owner, delivery need, cost code, and attachments, making triage easier than searching across inboxes and chat threads.
Adapt it to the shipment
Start with the request closest to your workflow, then replace sample service levels, inventory choices, and routing rules with the options your team actually supports.
Collect employee identity, cost center, recipient address, package size, deadline, and attachments before the parcel reaches the counter.
Capture pallet details, facility hours, dock conditions, appointments, handling needs, and documents for a useful carrier quote or booking review.
Connect order references, return items, pickup addresses, packaging status, preferred dates, and damage photos in one customer-friendly path.
Tie samples to an opportunity or event, request inventory quantities, record a must-arrive date, and identify whether materials need to come back.
Build the workflow
Describe your shipment types and decision points, review the generated fields, then connect each complete submission to the people who quote, pack, book, and track it.
Name who requests shipments, what commonly moves, where it originates, and which team fulfills it. Include the exceptions that change the questions, such as international, freight, return, or expedited work.
Replace generic choices with real warehouse locations, service preferences, budget codes, and handling options. Mark booking-critical inputs required and hide specialist fields until their condition applies.
Set notifications for the mailroom, logistics desk, warehouse, or returns team. Include the request reference and urgency so recipients can triage without reopening every field manually.
Use submission status, a connected sheet, or your automation workflow to record review notes, carrier choice, tracking number, and dispatch date alongside the original request.
Form vs email vs label
A label tool serves the packing desk after shipment data is known. A shipping request form serves the earlier handoff: it collects the business need and operational details so the team can review, quote, and book.
Field guide
The best field list follows the decisions your shipping team makes. Use these six groups as a practical baseline, then remove anything that does not affect review, packing, service choice, cost allocation, or delivery.
Requester and ownership
Start with a named requester, reachable contact, team, and business purpose. That gives the logistics coordinator somewhere to resolve questions and makes cost or priority review possible before work begins.
Origin and destination
Separate sender, pickup, and recipient data into structured fields rather than one long text box. Include the human contact and operating constraints that determine whether a driver can actually collect or deliver.
Contents and quantities
The item description should help someone select packaging and identify restrictions, not merely repeat an internal nickname. Repeatable item groups work well when one request contains several products or documents.
Packages and handling units
Item count is not package count. Ask how the goods will be packed and collect dimensions and weight for each carton, pallet, crate, or envelope so the team can compare appropriate services.
Dates and service intent
A word such as urgent does not reveal transit time. Ask when goods are ready, when the recipient needs them, and whether the date is flexible. Logistics can then assess a service level without guessing.
Documents and internal follow-through
Packing lists, invoices, photos, item sheets, and customer instructions often arrive in separate threads. Upload fields and a stable request reference keep that context attached while the request moves through review.
Related tools
Connect address collection, ordering, returns, purchasing, and file intake with focused forms that support the same operations workflow.
Collect structured delivery destinations when address intake is the primary job.
Open toolGather purchasing details that may need to precede supplier fulfillment and delivery.
Open toolCapture returned items, reasons, and customer context before arranging reverse logistics.
Open toolCollect packing lists, product sheets, photos, and shipment documents in a dedicated intake.
Open toolRequest inventory or materials before the warehouse prepares them for movement.
Open toolCreate a structured order intake for goods that will be prepared and delivered.
Open toolFAQ
Practical answers for logistics coordinators, office managers, warehouse teams, and customer operations staff designing shipping intake.
A shipping request form is an intake form used before a parcel, pallet, document, sample, order, or return is booked. It collects who requested the shipment, where it starts and ends, what is moving, how it is packed, when it must arrive, how costs are assigned, and which exceptions need review. The submission becomes a consistent handoff to the mailroom, warehouse, fulfillment, or logistics team.
At minimum, collect requester contact, department or cost owner, recipient name and complete address, recipient phone, item description and quantity, package count, dimensions and weight, pickup-ready date, requested arrival date, service preference, declared or reference value when your workflow uses it, and special handling notes. Add a project, customer, order, or event reference when the shipment needs to be reconciled later.
Begin with a domestic-or-international choice. Keep the domestic path concise, then conditionally show destination country, detailed contents, quantity, unit value, total value, country of origin, reason for export, and supporting-document uploads for the international path. Your shipping or trade team should decide which data and documents are required for the particular goods and lane; the form's job is to collect their defined inputs consistently.
Yes, if the first questions identify shipment type and reveal the appropriate branch. Parcel requests can ask for carton size and service speed. Freight can ask for pallets, freight class if known, stackability, dock access, liftgate, and appointments. Returns can ask for an order reference, return items, packaging availability, reason, pickup preference, and damage photos. Separate forms may still be clearer when different teams own those workflows.
Make booking-critical fields required, label units beside dimensions and weight, split addresses into components, provide examples for content descriptions, and use dropdowns for supported warehouses, cost centers, and service preferences. Conditional logic prevents irrelevant questions while ensuring special cases receive extra scrutiny. Include an end-of-form review reminder for the delivery address, deadline, package measurements, and attachments before submission.
Yes. Makeform provides unlimited free forms and responses, so you can generate, edit, publish, and use the shipping request form without a response cap. The paid tier removes the Makeform badge. You can keep the free version in service for recurring staff or customer shipping intake.
Build the routing data into the form: shipment type, origin site, destination country, requested speed, package size, and return status. Those answers can support notifications or connected workflows for the mailroom, warehouse, international desk, returns team, or an expedited reviewer. Keep a visible fallback owner for unusual requests so a submission does not sit unassigned when it misses the usual rules.
A useful process acknowledges receipt, assigns a stable request reference, sends the submission to the responsible queue, checks address and package data, resolves restrictions or approval needs, selects a carrier and service, and records the tracking number. Tell requesters that submission starts review rather than promising pickup or delivery. Share status and tracking through the channel your team actually maintains, and retain the original request beside later booking details.
Replace scattered shipping messages with one complete handoff.
