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
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:- Customer places an order
- storekit attempts to send the order to your POS
- If the POS accepts it → Order flows through your normal POS workflow
- If the POS fails → Order prints immediately on your storekit printer
Setting Up Fallback Printing
Simply connect a storekit cloud printer 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.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
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.Fallback printing is a safety net, not a long-term solution. If you’re seeing frequent fallback tickets, see Troubleshooting to diagnose the underlying issue.