Reference · built on requestOperator by FibricOrders & fulfillment

Short Pick

Reads short-pick exceptions from the warehouse against the order lines, then proposes a substitute, a backorder line, or ship-short.

Request accessPricing ↗

About

A picker reaches the bin and the last unit is not there. Short Pick reads that exception as the warehouse reports it, the order line it belongs to, stock for the same SKU at other locations, the next purchase order date, and the substitute rules you keep for that product family.

It proposes one of three paths for the short line: a substitute with the price difference and a message asking the customer to accept, a backorder line held with an expected date, or ship-short with a partial fulfillment and a refund for the missing quantity. A person approves, the warehouse channel gets the decision in a thread on the order, and the customer gets one message that says what shipped and what did not.

This is a reference listing. It documents what Fibric would read from Short Pick and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • ShipHero Order Backorder and Order Deallocated webhooks, and Tote Complete events that report fewer units than the order line
  • Logiwa PickingCompleted, InventoryAllocated, and AllocationCancelled events for the shipment order
  • The order lines in Shopify: remainingQuantity on each FulfillmentOrderLineItem and the customer's contact details
  • Stock for the same SKU at other locations, and the next purchase order date for it
  • Substitute rules you maintain: which variants or products may replace which, and at what price difference
  • Open support tickets on the order, so the customer is not told two different things

Proposed actions

  • Target capability: propose a substitute line: the replacement SKU, the price adjustment, and the message asking the customer to accept
  • Target capability: propose a backorder line: keep the unit on the order under a fulfillment hold with the expected date from the purchase order
  • Target capability: propose ship-short: a partial fulfillmentCreate for the picked units and refundCreate for the short quantity
  • Target capability: propose a Slack message to the warehouse channel, threaded on the order, with the SKU and the decision to act on
  • Target capability: propose a Postmark email to the customer stating what shipped, what did not, and the refund or the new date

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Ship what was picked, refund the gap

    A ShipHero backorder on one line gets a proposal to fulfill the other Shopify lines now and refund the short quantity, with the Postmark email to the customer drafted.

    With ShipHero, Shopify, Postmark

  • Offer the variant on the shelf

    When the substitute table lists another colour that Logiwa shows in stock, propose the swap on the WooCommerce order with the price difference and the acceptance message before anything ships.

    With Logiwa, WooCommerce

  • Tell the floor in the thread

    Each decision is proposed as a Slack message in the warehouse channel, threaded on the ShipHero order number, so pickers see the outcome without opening a second system.

    With Slack, ShipHero

Requirements

  • A warehouse system that reports short picks or backorders as events: ShipHero or Logiwa
  • A store connector that can fulfill part of an order and refund a line: Shopify or WooCommerce
  • Stock by location and purchase order dates for the SKU, from the warehouse system or your inventory tool
  • Substitute rules per product family, or a decision that substitutes are never offered
  • A messaging path for the warehouse and for the customer: Slack and Postmark
Authentication
A warehouse API token for ShipHero or Logiwa, a Shopify app token with fulfillment and refund write scopes, a Slack bot token with chat:write, and a Postmark server token.

Limits

  • A short pick is as reliable as the warehouse event; a miscount corrected on the floor withdraws the proposal
  • Substitutes come from your rules; the customer must accept before the line changes
  • A partial fulfillment ships the picked units; the short units stay on the order until a person chooses a path
  • Refunds for a short line follow the order's payment; split tenders or gift cards may need the store's own refund order

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Short Pick ↗

Questions and answers

What does the approver choose between?
One path per short line: substitute, backorder, or ship-short with a refund. The proposal shows the warehouse event, the line and quantity, stock elsewhere, the next receipt date, the substitute rule if any, and the messages that would go out.
What does the order line keep?
The order line carries the path, the partial fulfillment or the hold, the refund or the substitute accepted, the approver, and the time. The Slack thread and the customer email are linked from the same entry.
Would it fulfill, refund, or message anyone unprompted?
No. Fulfilling, refunding, swapping a line, and messaging are proposals until a person approves them, and an approved one is carried out once. A short pick with no matching order line is listed as unmatched for the warehouse to resolve.
Ask about Short Pick

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy