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

# Fallback Printing

> Automatically print storekit orders if your POS integration fails. Fallback printing ensures orders still reach the kitchen when the POS connection drops out.

If you're integrated with a POS system, orders normally flow directly to your POS for preparation and printing. But what happens when that connection fails? Fallback printing ensures orders still reach your kitchen.

## The Problem

POS integrations can fail for various reasons:

* POS server is down or unreachable
* Network issues between storekit and your POS
* POS rejects the order (menu sync issues, item not found)
* Timeout during busy periods

When this happens, the order is paid and confirmed to the customer - but your kitchen doesn't know about it. This leads to missed orders, unhappy customers, and lost revenue.

## The Solution: Fallback Printing

With a storekit cloud printer connected, you can configure orders to print automatically when they fail to reach your POS.

**How it works:**

1. Customer places an order
2. storekit attempts to send the order to your POS
3. If the POS accepts it → Order flows through your normal POS workflow
4. If the POS fails → Order prints immediately on your storekit printer

This gives you a safety net - even if your POS is down, you'll still receive a printed ticket.

## Setting Up Fallback Printing

Simply [connect a storekit cloud printer](/guides/printing/printer-setup) to your store. Once connected, failed POS orders will automatically print - no additional configuration required.

The printer should be set to **manual print** mode (the default). This means regular orders won't print (your POS handles those), but failed orders will print automatically as a fallback.

<Tip>
  Position the printer somewhere visible - like the pass or expediting station - so staff immediately notice when a fallback ticket appears.
</Tip>

## What Gets Printed

Fallback tickets include:

* All order details (items, modifiers, quantities)
* Customer details and contact info
* Fulfillment method and time
* **Clear "POS FAILED" warning** so staff know this order bypassed normal flow

The ticket format matches your regular storekit print settings.

## Best Practices

### Always Have a Fallback

Even if your POS integration is rock-solid, connect a storekit printer as insurance. The cost of a printer is nothing compared to missing orders.

### Position the Fallback Printer Strategically

Put it somewhere visible - not tucked away in a corner. Staff need to notice when a fallback ticket prints.

### Train Your Team

Staff should know:

* What a fallback ticket looks like
* That it means the POS didn't receive the order
* To manually enter it into the POS if needed for reporting
* To alert a manager if fallback tickets become frequent

### Review Failed Orders Daily

Don't just print and forget. Review your failed orders report regularly to catch integration issues before they become major problems.

<Note>
  Fallback printing is a safety net, not a long-term solution. If you're seeing frequent fallback tickets, see [Troubleshooting](/guides/printing/troubleshooting) to diagnose the underlying issue.
</Note>