Auto Print Engine
Internal Support & Training Guide
Purpose
The Auto Print Engine allows locations to automatically print customer-facing documents based on specific triggers, filters, schedules, and printer destinations.
This feature is designed for:
- Additional printing workflows
- Conditional printing workflows
- Specialized operational printing needs
This feature works alongside existing terminal printing settings and is not intended to replace standard receipt printing behavior.
The most common use case is:
- Automatically printing a combined customer receipt when a delivery order is dispatched to a driver.
Navigation
POS → System Setup → Auto Print Rules
From this page support can:
- Create new rules
- Edit existing rules
- Activate/deactivate rules
- View audit history
- Filter/search rules
- Bulk edit rules
Important Behavior Notes
Multiple Rules Can Trigger Simultaneously
The Auto Print Engine does not prioritize or suppress duplicate rules.
If multiple rules match the same trigger, all matching rules will print.
Example
Rule 1:
- Print Combined Receipt on Send
Rule 2:
- Print Combined Receipt on Send for To Go Orders
Result:
- A To Go order would print two receipts
No Rule Priority
Rules are evaluated independently.
There is:
- No priority order
- No conflict handling
- No duplicate prevention
Support should carefully review all active rules to avoid unintended duplicate printing.
Rules Are Evaluated at the Moment of the Trigger
Rules are checked only when the trigger occurs.
The engine does not continuously monitor the order afterward.
Example
A rule requiring:
- Delivery Order Type
- Driver Job Role
Will only evaluate those conditions at the exact moment the Dispatch trigger occurs.
Location Specific
Auto Print Rules are configured per location only.
Rules do not apply across multiple locations automatically.
Creating an Auto Print Rule
Each rule contains five major sections:
- Identity
- Triggers
- Documents
- Filters
- Schedule
At least:
- 1 Trigger is required
- 1 Document is required
Identity Section
Name
Internal name used to identify the rule.
Best Practice:
Use descriptive naming.
Examples
- Dispatch Combined Receipt
- Bar Close Receipt
- Driver Receipt Print
- OLO Dispatch Receipt
Destination Printer
Determines where the document prints.
Options
Originating Device
Prints to the device where the action occurred.
Example:
- Order dispatched on POS 2
- Receipt prints at POS 2
Specific Printer
Forces the document to print at a designated printer regardless of where the action occurred.
Example
A restaurant wants all dispatch receipts to print at the host stand printer:
- Destination Printer = POS 1
Even if the order is dispatched from another terminal, the receipt prints at POS 1.
Important Note
If the destination printer is offline or unavailable:
- The document will not print.
Triggers
Triggers determine when the rule evaluates and prints.
Send Trigger
Prints anytime:
- An item is initially sent
- An item is voided/removed
This generally means:
- Any time items are first rang in
- Any time an item is removed through a void
Compatible Documents
Customer Receipts
Supported.
Payment Vouchers
Technically supported but generally not recommended.
There is currently no practical operational use case for this setup.
Unexpected printing behavior may occur in edge cases.
Custom Fragments
Supported.
Send Trigger Notes
Because Send triggers on void activity:
- Additional receipts/fragments may print after changes to the order.
Payment Trigger
Prints each time a payment/tender is applied.
This includes:
- Split payments
- Partial payments
- Multiple guest payments
Important Behavior
If 3 guests pay separately:
- The rule triggers 3 separate times.
Compatible Documents
Customer Receipts
Supported but rarely recommended.
In dine-in environments this may cause excessive receipt printing during split payments.
Payment Vouchers
Typically only useful if:
- Credit card voucher printing has been disabled at the terminal level.
Otherwise the terminal already prints credit card vouchers automatically.
Custom Fragments
Supported.
Closed Trigger
Prints when the ENTIRE order is fully paid and closed.
Important Behavior
If a closed order is reopened and closed again:
- The rule triggers again.
Compatible Documents
Customer Receipts
Supported.
Payment Vouchers
Only recommended if terminal-level voucher printing is disabled.
Important limitation:
- Only the LAST credit card voucher used on the order will print when the order closes.
Custom Fragments
Supported.
Dispatch Trigger
Prints when an order is dispatched to a driver.
Dispatch occurs when:
- The order is assigned to a driver.
Most Common Use Case
This is the most common and recommended Auto Print setup.
Example
- Trigger = Dispatch
- Document = Combined Customer Receipt
- Destination Printer = Driver/Dispatch Printer
This allows delivery receipts to print automatically when drivers are assigned.
Compatible Documents
Customer Receipts
Supported.
Payment Vouchers
Supported.
Custom Fragments
Supported.
Documents
Documents determine what prints.
Multiple document types may be selected on the same rule.
Customer Receipts
By Seat
Prints:
- One receipt
- Entire order
- Guests separated by seat
Combined
Prints:
- One receipt
- Entire order
- Like items combined together
- No seat separation
This is the most commonly used receipt format for dispatch printing.
Individual
Prints:
- One receipt per guest/seat
Example
3 guests = 3 receipts
Important Limitation
“Selected Guest” printing is not supported.
Because triggers often occur without a currently selected guest, the system cannot determine which guest receipt should print.
Payment Vouchers
Includes:
- Customer Copy
- Merchant Copy
Important Support Guidance
Payment Voucher auto printing is generally only needed when:
- Terminal-level credit card voucher printing has been disabled.
Otherwise:
- Credit card vouchers already print automatically during payment processing.
Custom Fragments
Custom Fragments allow locations to print custom receipt content independently from standard receipts.
Common Uses
- Delivery instructions
- Promotional messaging
- Custom operational notes
- Specialized customer messaging
Setup Location
Custom Fragments are configured in:
POS → System Setup → Receipt Setup
Support must create the Custom Fragment before it can be used in an Auto Print Rule.
Filters
Filters determine which orders qualify for the rule.
If multiple filters are selected:
- ALL conditions must be true.
Filters use AND logic.
Important Filter Behavior
If no filters are selected:
- The rule applies to ALL orders.
Context Filters
Used when additional filtering logic is needed.
Most useful for:
- Include/Exclude logic
- Device Types
- Brands
- Guest Count Ranges
Important Note
Location filtering inside Context Filters does not matter because Auto Print Rules are already location specific.
Tenders
Used to limit rules by payment type.
Important Limitation
Tender filtering only applies to:
- Payment trigger
- Closed trigger
Tender filters do NOT affect:
- Send
- Dispatch
Zones
Limits printing to specific restaurant zones.
Example
Print customer receipts on close only in the Bar zone.
Job Roles
Limits printing based on employee job role.
Example
Print dispatch receipts only when the Driver job role dispatches the order.
Order Types
Limits printing to specific order types.
Example
Only print customer receipts for Delivery orders.
Profit Centers
Limits printing to orders belonging to a specific profit center.
Example
Print receipts only for Online Ordering sales.
Devices
Limits rules based on the originating device.
Example
Only print close receipts from POS 2.
Schedule
Schedules determine when rules are active.
Days
Select which days the rule applies.
If days are checked but times are blank:
- The rule applies all day.
Time Ranges
Rules may be restricted to specific times.
Example
- Only print during dinner hours
- Only print during delivery shifts
Overnight Schedules
Schedules can cross midnight.
Example
8:00 PM – 2:00 AM
Timezone
Schedules use the local device/store timezone.
Active vs Inactive Rules
Rules may be activated or deactivated using the Active toggle.
Inactive rules:
- Remain saved
- Do not evaluate
- Do not print
Recommended/Common Setup
Dispatch Combined Receipt
Most common setup:
- Trigger = Dispatch
- Document = Combined Customer Receipt
- Destination Printer = Dispatch/Driver Printer
Commonly used by:
- Pizza restaurants
- Delivery-heavy operations
Configurations Support Should Avoid
Send + Payment Voucher
Technically works but generally has no operational value.
May produce unexpected or confusing printing behavior.
Payment Trigger + Customer Receipts
Can create excessive receipt printing during split payments or multi-guest payment situations.
Usually not recommended for dine-in environments.
Troubleshooting
If a document does not print:
- Verify the rule is Active
- Verify the correct trigger occurred
- Verify at least one document type is selected
- Verify all filters matched
- Verify schedule/day/time matched
- Verify the destination printer is online
- Verify printer assignments/configuration
- Verify another overlapping rule is not causing confusion
- Verify expectations do not conflict with standard terminal printing behavior
Best Practices
- Use descriptive rule names
- Avoid overlapping rules whenever possible
- Carefully review all active rules before adding new ones
- Use Dispatch + Combined Receipt for delivery workflows
- Use filters to reduce unnecessary printing
- Test rules in real operational scenarios before rollout
- Remember Auto Print supplements normal printing behavior