> ## Documentation Index
> Fetch the complete documentation index at: https://storekit.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Order Code Generation

> Configure how storekit generates short order codes used at pickup, on tickets, and in customer comms. Choose sequential, daily reset, or randomised.

Order codes are short identifiers used to reference orders at pickup, on printed tickets, and in customer communications. storekit supports different generation strategies to suit your operational needs.

## What Are Order Codes?

Each order receives a random code (e.g., "A1B2", "7X9K") that:

* Appears on the customer's order confirmation screen
* Prints on kitchen tickets
* Is used to call out orders for collection
* Helps staff quickly identify orders

## Code Types

storekit offers two order code formats:

### Alphanumeric (Default)

Random alphanumeric codes like `A7X2`, `K9B4`, `M3P8`.

| Pros                       | Cons                                     |
| -------------------------- | ---------------------------------------- |
| Short and easy to call out | Codes can repeat                         |
| No predictable pattern     | Some characters sound similar (B/D, M/N) |
| Works well at any volume   |                                          |

**Best for:** Most operations - simple, clean codes that work well for verbal callouts.

### Numeric Sequence

Sequential numbers like `0001`, `0002`, `0003`.

With numeric codes, you choose a **reset policy** - when the sequence restarts:

| Reset      | Behaviour                    | Best For                                               |
| ---------- | ---------------------------- | ------------------------------------------------------ |
| **Daily**  | Resets to 1 each day         | High-volume operations, seeing daily order count       |
| **Weekly** | Resets to 1 each week        | Operations referencing orders across days              |
| **Never**  | Never resets, counts forever | Tracking lifetime order count, guaranteed unique codes |

| Pros                                 | Cons                                      |
| ------------------------------------ | ----------------------------------------- |
| Easy to call out verbally            | Numbers get long over time (with "Never") |
| Shows order volume at a glance       | Predictable pattern                       |
| Customers find them easy to remember |                                           |

**Best for:** Quick-service restaurants, cafes, and operations that want to see order counts.

## Order Code Prefixes

Add a prefix to your order codes to make them instantly identifiable and easier to reconcile across systems.

### Why Use Prefixes?

**Distinguish from other platforms**

If you receive orders from multiple channels (storekit, Deliveroo, Just Eat, Uber Eats), they may use similar code formats. A prefix makes it immediately clear where an order originated:

* `SK-A7X2` - storekit order
* `A7X2` - Could be Deliveroo, Just Eat, etc.

**Easier reconciliation**

When matching orders across your POS, accounting software, or reporting tools, prefixes help filter and identify storekit orders quickly.

**Multi-location identification**

For brands with multiple sites, prefixes distinguish which location received the order:

* `NYC-0042` - New York
* `LON-0042` - London
* `MAN-0042` - Manchester

### Configuring Prefixes

1. Go to **Store Settings > Operations**
2. Find **Order Code Prefix**
3. Enter your preferred prefix (e.g., "SK", "WEB", or your store code)
4. Save changes

The prefix appears before the generated code, typically separated by a hyphen.

<Tip>
  Keep prefixes short (2-4 characters) to avoid making codes too long to call out or display.
</Tip>

## Configuring Order Codes

1. Go to **Store Settings > Operations**
2. Find **Order Sequence Policy**
3. Choose your code type:
   * **Alphanumeric** (default) - random codes
   * **Numeric** - sequential numbers with reset policy (Daily, Weekly, or Never)
4. Optionally set a prefix
5. Save changes

## Multi-Location Considerations

For brands with multiple locations:

* **Use prefixes** - Add location codes (e.g., "NYC-", "LON-") to distinguish orders
* **Separate sequences** - Each location maintains its own sequence
* **Shared format** - Keep the same strategy across locations for consistency

## Best Practices

1. **Match your callout method** - If you call order numbers verbally, use short codes
2. **Consider your volume** - High volume needs more unique codes
3. **Avoid ambiguity** - Remove characters that sound alike when called out
4. **Test thoroughly** - Place orders and verify codes appear correctly everywhere
5. **Train staff** - Ensure everyone knows how to read and call out codes

## Troubleshooting

### Duplicate Codes

If you're seeing the same codes causing confusion:

* **Alphanumeric codes** can repeat - this is normal. Consider adding a prefix to help distinguish orders.
* **Numeric codes with Daily/Weekly reset** will repeat after the reset period. Switch to "Never" if you need unique codes.
* Verify timezone settings match your operation (affects when daily/weekly resets occur).

### Confusion at Pickup

If customers can't find their orders:

* Consider adding a prefix to distinguish storekit orders from other platforms
* Train staff on clear verbal callout technique
* Display codes prominently on tickets and screens