Authenticate with your Grasshopper Labs credentials to access the manifest utility.
Account
Retailer & region
Orders are pulled only for this retailer (account). Saved on this device and reused next time.
Step 1
Upload files
Upload whichever you have — file type is detected automatically:
MXD Delivery (orders) only → create & cancel; MXD ASN trailer file(s) only → build the manifest; or both for the full flow.
Drag & drop .XLS / .XLSX files here
or click to browse
Step 2
Orders & status
Step 3
Cancel orders not on the file
These are pending in Grasshopper but not on today’s delivery file. Select which to cancel, then cancel them — or skip. Cancelling cannot be undone.
Step 4
Inbound manifest
Inbound SKUs (from ASN)
Inbound Manifest (line items, FIFO)
Create inbound manifests in Grasshopper
One manifest is created per ASN file, each named from its own trailer ids and containing the orders & line items matched to that file.
Create fulfillment manifest
Line items that could not be matched to the ASN files (SKU not inbound, or quantity exhausted). Review the toggles — only the selected items go on the -PENDING-INVENTORY-FULFILLMENT manifest. Rows where the same SKU appears on several orders start unselected: pick which order(s) should get it.
Behind the scenes
Decision log
Every keep, cancel and match decision in plain language. Search by order #, order ID, or SKU.