Order Fulfilment

Please add the ability to search or filter open orders by scanning or entering a product barcode in the main Orders tab. Use Case / Business Need: Our business operates on a special-order model where we do not hold inventory or pick from standard pick lists. When stock arrives at our warehouse, staff need to scan the incoming product's barcode to instantly pull up any open customer orders containing that item. Currently, with hundreds of open orders, staff cannot easily identify which order an incoming item belongs to. Adding a barcode search filter to the Orders list would streamline our inbound receiving workflow and significantly reduce order fulfillment time.

Packing Summary - have its own printing setting in settings > printing > advanced and on Print App

As a user, I would like to continue to use my scanner through my packing process which would include being able to scan a barcode that gets the weight from my integrated scales.

## 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.