There are three ways to create an order in Grasshopper. Pick whichever fits your workflow.

Manual order entry

Best for one-off orders, troubleshooting, or testing. Goes through the UI form.

  1. From any screen, click + New Order in the top right
  2. Fill in the consignee details: name, address, and primary contact phone
  3. Select the service level (White Glove, Threshold, Curbside, etc.)
  4. Add line items by SKU. The system will auto-fill weight and cube if the SKU exists in your catalog
  5. Optionally pick a vendor and FOB origin for each line item
  6. Click Create order. The order lands in status Pending Pickup or Pending Arrival
Reference order numbers must be unique

Your PO or reference number has to be unique across your shipper account. If you try to create an order with a duplicate, you'll get an error. Use a prefix per source system if you're consolidating from multiple OMSs.

EDI import

The most common path for retailers integrated through SPS Commerce, direct EDI, or trading partners like Wayfair and Electrolux. Orders arrive as 940s or equivalent and are auto-mapped.

EDI configuration is handled in Settings → EDI Partners. Once a partner is configured, no manual action is needed; orders appear in your queue automatically.

CSV upload

For bulk loads from systems that don't have EDI. Common for migration or seasonal pushes.

  1. Go to Orders → Import
  2. Download the CSV template
  3. Fill in your rows and upload
  4. The system validates first and shows you any errors before commit

API

For full programmatic integration, use the POST /api/orders/ endpoint. The API accepts the same fields as the manual form but lets you create orders at any scale. See the API getting started guide for the full walkthrough.

What happens next

Once an order is created, it flows through these high-level milestones:

  1. The order is assigned to the appropriate hub based on destination zip
  2. If FOB, freight is picked up from the vendor and brought to the hub
  3. The customer is invited to schedule (or the date is pre-confirmed depending on your config)
  4. On the day of delivery, the order is loaded onto a route and tracked live
  5. POD is captured, assets are attached, and the order moves to terminal status

For the full status reference, see Understanding order statuses.

Related articles

Understanding order statuses
What every order status means and how status transitions work.
6 min
Editing an existing order
Which fields can be changed before the order is loaded for delivery.
4 min
EDI partner configuration
Setting up EDI partners like Wayfair, SPS, and Electrolux.
8 min