Skip to content

Short picks and pick locations

Two store-floor changes that share a screen: what the customer is told when staff can't pick an item, and where staff record where items are kept. No mock-up was made; this records what shipped and why.

The "items weren't available" email

templates/shop/email/orderItemsUnavailable.html (and -text), in the shop design, built only from email/layout fragments: banner, orderMeta, section, text and items, as the part cancellation email is.

  • One email, not one per item. A picker can short three lines in a minute. The email goes once, when the order is marked ready or packed (or handed over or sent without that), and lists every item not yet told about. An item found short after that, or a short that cancels the whole order, is told straight away, since there is no later moment.
  • Money first, in the customer's terms. After an apology, one sentence says what happens to their money, whichever applies: refunded to their card, not charged (an authorised payment is captured less), or handed back in cash when they collect. Amounts are minor units formatted in the template with #shopMoney.
  • Two lists: Not available (the short items) and Still coming (the rest), so the customer can see the order as it now stands. A whole cancellation says so and has no second list.
  • Swaps. Where the shop allows substitutes, a third list, Picked in place of what you ordered, says "2 x Cup, in place of Mug", after a sentence that the customer won't pay more. The apology for items not coming shows only when something isn't.
  • Nothing internal. The reason (out of stock, damaged) and staff's note are never in it.
  • A greeting without a name. An order with no first name is greeted "Hi there," rather than "Hi ,", as the subscription emails do.
  • Words are email.shortPick.*, in English and Spanish; the render test is in OrderEmailsDesignRenderTest.

What a line is called

Every shop email and the admin order page name a line by DLineItem.displayName (with displayNameKey, a message to look up, for a till quick payment): the label staff typed for a till's custom amount ("Raffle tickets"), In-store payment for a quick payment, otherwise the product's name. Before, only the order confirmation did this, so the other emails called a custom amount by the hidden till item it is sold as. The admin page also says what a substitute was picked in place of. CustomLineEmailsRenderTest renders every shop email that lists lines with a custom line, and fails on a template that prints a line's product name directly.

"Where it's kept" on the admin

  • Product Stock tab: the location grid gains a Where it's kept column, three short text fields (aisle, bay, shelf) per location, the same bx-input width as the stock figure beside them. A hidden field records what was shown, so saving the product only writes locations whose fields changed, as the stock figures already work. The walk sequence isn't here: it is a whole-store ordering, set in bulk.
  • Location page: a Where things are kept card, outside the location form so importing never posts its unsaved fields. Download CSV and Import, with the result in a callout: how many were saved and removed, and each problem row by line number. The CSV is the spreadsheet a store already keeps, so it is the main way places are set.
  • The admin render test for the grid is ProductStockPanelRenderTest.