Order Fulfilment

## Request Please add a Shopify writeback option for Local Delivery orders similar to the existing "Mark pickup in store orders as ready for pickup" option. ### Current behaviour When we scan and pack a Shopify Local Delivery order in Starshipit, Starshipit currently writes the order back to Shopify as fulfilled/delivered. This is too far along in Shopify's Local Delivery workflow. Our actual workflow is: Order is packed in Starshipit. Shopify should show the order as Prepared / Ready for delivery . We physically deliver the order ourselves. We manually click Mark as delivered in Shopify after the delivery has actually been completed. At the moment, step 2 is being skipped and Starshipit effectively performs step 4 when the parcel is packed. ## Requested option Please add a setting similar to: Mark local delivery orders as ready for delivery When enabled: * Detect Shopify fulfillment orders where deliveryMethod.methodType = LOCAL . * When Starshipit writeback occurs after packing, transition the Shopify Local Delivery order to its prepared for local delivery / ready for delivery state. * Do not mark the order as DELIVERED . * Leave the final Mark as delivered action for the merchant to complete later in Shopify. This could sit alongside the existing: Mark pickup in store orders as ready for pickup ## Shopify developer information Shopify exposes Local Delivery through the FulfillmentOrder GraphQL object and identifies the method using: deliveryMethod.methodType = LOCAL Shopify also exposes the webhook: fulfillment_orders/line_items_prepared_for_local_delivery This event occurs when a fulfillment order's line items have been prepared for local delivery. For comparison, Shopify's pickup workflow has the GraphQL mutation: fulfillmentOrderLineItemsPreparedForPickup As of the Shopify Admin GraphQL API 2026-07, Shopify does not appear to expose an equivalent public fulfillmentOrderLineItemsPreparedForLocalDelivery mutation. Starshipit's development team may therefore need to confirm with Shopify which supported method third-party order management apps should use to trigger the native Prepared for delivery state. The important part for us is that packing a Local Delivery order in Starshipit should not create a DELIVERED fulfillment event . A DELIVERED event should only occur once the parcel has physically been delivered.

Recommended Packaging can assign multiple packages to an order, but it does not show which items have been allocated to each package. Add item-to-box allocation details so packers can see which SKUs or quantities should go into each recommended box, either on the order, packing summary, or packing slip. Example: Box 1: X-Large contains items A and B Box 2: Medium+H contains item C This would help customers using Recommended Packaging for multi-box orders confirm how the algorithm expects the order to be packed.

Please allow Packing Validation to scan and validate products using the SKU field. For many merchants, SKU is the most reliable product identifier because it is controlled internally. In our warehouse, we print and label products with our own SKUs, then use those SKU labels for picking and packing. The issue is that Packing Validation currently appears to only support product barcode scanning. This does not work well for us because only around 50% of our products have manufacturer barcodes, but every product has a SKU. Starshipit already shows the SKU on the order item line, so the data is already available inside the order. We need Packing Validation to let us scan the SKU and match it against the SKU field on the order.

Currently, StarShipIt writes back the order status, tracking number, carrier name, and fulfilment location to Shopify when a label is generated, but the packaging type used for the order is not included in this writeback. We would like the option for StarShipIt to write the packaging name back to Shopify as an order note attribute (or similar field) at the time of dispatch. Use case: We need to track how many of each packaging type (boxes, satchels, mailers, etc.) we are consuming across our orders to manage consumables stock. While this data exists within StarShipIt's reporting, having it written back to Shopify would allow us to consolidate reporting and make it accessible alongside other order data without needing to export from multiple platforms. Ideal implementation: A toggle in Settings > Integrations > Shopify Settings to enable packaging writeback The packaging name written to a Shopify order note attribute (e.g. "Packaging: Large Box") or as an order tag

Currently most variants don't show in packing validation. Please show all shopify options so we can validate items that dont have barcodes are are loose. see example photos attached

Support outer barcode and inner barcode, so that we can scan the product in a carton rather than repeat scan the items all the time.

Add the option to mute or disable the packing validation sounds.

When the customer is using the %OrderNumber% value on the packing slip and they merge orders, it will show the order numbers that were merged into the Parent order.

Currently, StarShipIt writes back the order status, tracking number, and carrier name to Shopify when a label is generated. However, the actual cost paid to the carrier for the shipment is not included in this writeback. We would like the option for StarShipIt to write the carrier shipping cost back to Shopify as an order note attribute or metafield at the time of dispatch. Use case: Shopify already records the shipping amount charged to the customer at checkout. If the actual carrier cost from StarShipIt were written back alongside this, we could run shipping margin reports directly within Shopify and compare what the customer paid vs what we paid the courier, per order. This would allow us to identify where we are subsidising shipping, which services or zones are most costly, and where our shipping pricing may need adjustment. At the moment, this data exists in StarShipIt's reporting and in Shopify separately, with no way to bring them together without a manual export and reconciliation process. This breaks the reporting workflow for any merchant trying to understand their true shipping margin. Ideal implementation: A toggle in Settings > Integrations > Shopify Settings to enable carrier cost writeback The carrier cost is written to a Shopify order note attribute or metafield (e.g. "Carrier Cost: $8.45") so it is accessible in Shopify reports and downstream integrations This would be valuable for any merchant who wants to understand their shipping profitability without having to leave Shopify or reconcile data from multiple platforms.

1) an option to have an attribute for products that are "ship ready" ie don't need packaging into an outer package. 2) an option where products without dimensions are assumed to be "loose" items (ie not in a box) and if combined with other items that do have the dimensions, use the packaging logic for the second box (documentation says that if ANY item has no dimensions than the default package will be used).