Mark Shipping Status — Tutorials

Go to the Shopify App Store and search for "Mark Shipping Status", or install directly from the product page.

Click "Add app" and review the permissions screen. The app requires read orders, write orders, read all orders, and write fulfillments.

Click "Install" to approve permissions. The app installs and embeds into your Shopify Admin.

Open any order in Shopify Admin and scroll to the Fulfillment section — you should see the Mark Shipping Status action extension.

Confirm the status dropdown, Event Date field, and Note field are all visible.

Run a test update on a sample or low-value order to verify the Shopify order timeline reflects the event correctly.

Open the target order in Shopify Admin.

In the Fulfillment section, find the Mark Shipping Status action and click it to open the update panel.

Select a status from the dropdown. All 11 options are available: Confirmed, Label Purchased, Label Printed, Carrier Picked Up, In Transit, Out for Delivery, Attempted Delivery, Ready for Pickup, Delayed, Delivered, and Failure.

Event Date: leave blank to use the current time as happenedAt. If you need to backdate, enter the exact date and time.

Note (optional): add context such as a courier remark or exception detail. Notes appear in the order timeline.

Click Submit. The Shopify order timeline will update immediately with the new fulfillment event, including your note if provided.

When to use a custom event date: carrier confirmation arrived hours after the actual delivery, you are running a batch correction for yesterday's route, or you need to align the Shopify timeline with a third-party logistics record.

In the update panel (single-order or bulk), click the Event Date field and enter the date and time you want to record.

If you leave Event Date blank, Shopify records the current time. In your dashboard ledger this shows as "Default used".

If you enter a custom date, the ledger logs it as "Custom input" — so you always know which events were timestamped explicitly vs. defaulted.

Avoid using incorrect custom dates (e.g., future dates or dates before the order was placed) as this can cause timeline inconsistencies that are hard to correct later.

For bulk corrections: use the Event Date field on each row independently. You can set different happened-at times per fulfillment in a single bulk session.

Notes appear in the Shopify order timeline and are visible to all admins. They do not appear to customers.

Keep notes concise and factual. Include who, what, and where when relevant.

Handoff note example: "Handoff: Left at front desk, signed by Rina"

Exception note example: "Exception: Attempted delivery, customer unavailable — redelivery scheduled tomorrow"

Pickup note example: "Pickup: Ready for collection at Locker A12, ground floor"

Failure note example: "Failure: Address not found — contact customer to confirm delivery address before retry"

Avoid vague notes like "done" or "updated" — these add no operational value.

For teams with multiple operators, consider prefixing the note with the operator initials for quick accountability: "RK: Left at reception, building B".

Open the Mark Shipping Status app dashboard from Shopify Admin.

The dashboard lists fulfillments available for status updates. Use filters to narrow the set if needed.

Each row in the bulk view has its own status dropdown, Event Date field, and Note field. These are independent — setting a status on one row does not affect others.

If most rows need the same status, look for a "Set all to" shortcut at the top of the list. Override individual rows after to handle exceptions.

Common mixed-status pattern: set the majority of rows to Delivered, then change specific rows to Delayed or Attempted Delivery as needed.

Review all rows before submitting. Check that statuses, dates, and notes look correct.

Click Submit to process the batch. The app handles Shopify rate limits automatically.

After the run, check the ledger to verify all events were recorded. If any row failed, the ledger will indicate it and you can retry.

Issue: Status dropdown is not visible on the order → The app action extension may not be installed yet. Confirm the app is installed with full permissions. Try refreshing Shopify Admin.

Issue: Update returns a permissions error → The app may be missing one of the required OAuth scopes (read_orders, write_orders, read_all_orders, write_fulfillments). Reinstall or re-authorize the app from the Shopify App Store listing.

Issue: Event Date was accepted but the timeline shows a different time → Shopify displays times in the store's timezone. Your input is stored correctly — the display offset is a presentation difference.

Issue: Shopify shows "Failed delivery" but I set Failure → This is expected. Shopify renders the FAILURE API value as "Failed delivery" in the order timeline. The underlying status is correct.

Issue: Bulk run shows partial success → Some fulfillment updates may fail if the fulfillment is in an uneditable state or if a rate limit retry exhausted. Check the ledger for failed rows and retry individually.

Issue: Note is not visible in the order timeline → Notes only appear on fulfillment events, not on the main order activity feed. View the Fulfillments section of the order to see events and their notes.

Still having issues? Contact support at hello@greatindiancompany.com and include the order ID and error message if available.