# Claim Stubs & Bag Tags
> Source: https://development.fuze-store.com/docs/app/printer/claim-stubs-and-bag-tags

# Claim Stubs & Bag Tags

Some shops take the goods first and the money later — laundry, dry cleaning,
repairs, alterations. At drop-off there's nothing to receipt, because nothing
has been paid. What the customer needs is a **claim stub**: proof of what they
left with you, and how to get it back.

  Claim stubs currently switch on for stores created from the **Laundry**
  business type. Other drop-off trades — repair, tailoring — use a normal receipt
  for now. The document itself isn't laundry-specific, so if you run one of those
  and want claim stubs, let us know.

## Claim stub vs receipt

|                          | Claim stub                         | Sales receipt          |
| ------------------------ | ---------------------------------- | ---------------------- |
| **Printed**              | At drop-off                        | When they pay, at pickup |
| **Says**                 | What you're holding, what it costs | What was paid          |
| **An official receipt?** | No                                 | Yes                    |

Both come from the same order. The claim stub goes out first; the receipt
follows when the order is paid and completed.

## What's on the claim stub

- Your **store name, address, and phone**
- The **order number**, plus a scannable QR
- The **customer** and their phone
- What was dropped off
- **Ready by**, taken from the order note
- The **total** — and if they left a deposit, the **amount paid** and **balance
  due**

  Whatever the cashier types into the order note is what the customer reads as
  their ready-by. Agree on a house format ("Fri 3pm" beats "Friday") so every
  stub is consistent.

## Bag tags

Separately, print a tag per bag so items stay matched to their owner.

  
    The dialog asks **"How many bags does this order have?"**
  
  
    The button confirms what you're about to do — *Print 3 Tags*.
  
  
    Each tag prints numbered — "Bag 1 of 3" — so nothing gets separated.
  

Reprinting is just running it again, which you'll want when a tag comes off in
the wash.

## Scanning at pickup

Both documents carry a **claim QR**. Scan it with the Fuze Store app — from the
POS Scan action or the register scanner — and it opens that order directly, so
you're not searching by name. See
[Scanning QR codes & barcodes](/docs/store/pos/scanning-qr-and-barcodes).

The customer can also point their own phone camera at it to check their order
status on the web.

## Taking payment at pickup

Pull the order up, take payment, complete it. The sales receipt prints then. A
deposit taken at drop-off is already on the order, so the balance due is just
what's left.

## Reprinting a claim stub

Available from the order's print options until the order is finished. After
that, the sales receipt is the document that matters.

## Which printer

Both print on an ordinary **58mm or 80mm receipt printer**. No label printer and
no add-on required. If you'd rather have bag tags on adhesive die-cut labels,
that's the [Advanced Printing](/docs/app/printer/label-printing) path.

  Check a claim stub and a bag tag on your own printer and paper width before
  going live — particularly that the QR scans and the ready-by line reads the way
  you want.

## Related guides

- [Bag Tags & Batch Labels](/docs/app/printer/bag-tags-and-batch-labels)
- [Scanning QR codes & barcodes](/docs/store/pos/scanning-qr-and-barcodes)
- [Routing Rules](/docs/app/printer/routing-rules)