Start with how service runs across your team and locations, from first order to day close.
Define where service starts and who opens the order.
Owner: Your team owns the service entry point and staff role.
Recovery: Keep a manual intake path and name who resolves the block.
Decide who can adjust, split, cancel or transfer an order.
Owner: Your team sets permissions; OmniPay helps define the workflow.
Recovery: Keep the original order visible and name the approver.
Define where payment is accepted and which status returns to the order.
Owner: The provider owns the transaction; your team owns the order decision.
Recovery: Treat an unknown return as unresolved until its status is confirmed.
Name who checks totals and hands the day’s record to accounting.
Owner: Your team owns close and reconciliation.
Recovery: Separate exceptions from confirmed totals and assign follow-up.
A day at the counter
Set the owner and recovery path.
| 01Service beginsDefine where service starts and who opens the order. | 02Order changesDecide who can adjust, split, cancel or transfer an order. | 03Payment completesDefine where payment is accepted and which status returns to the order. | 04Day closesName who checks totals and hands the day’s record to accounting. | |
|---|---|---|---|---|
| Your team | Service entry point and staff role | Permissions | The order decision | Close and reconciliation |
| OmniPay | Helps define the workflow | |||
| Provider | The transaction | |||
| Recovery | Keep a manual intake path and name who resolves the block. | Keep the original order visible and name the approver. | Treat an unknown return as unresolved until its status is confirmed. | Separate exceptions from confirmed totals and assign follow-up. |
- 01
Service begins
Define where service starts and who opens the order.
- Your team
- Service entry point and staff role
- Recovery
- Keep a manual intake path and name who resolves the block.
- 02
Order changes
Decide who can adjust, split, cancel or transfer an order.
- Your team
- Permissions
- OmniPay
- Helps define the workflow
- Recovery
- Keep the original order visible and name the approver.
- 03
Payment completes
Define where payment is accepted and which status returns to the order.
- Your team
- The order decision
- Provider
- The transaction
- Recovery
- Treat an unknown return as unresolved until its status is confirmed.
- 04
Day closes
Name who checks totals and hands the day’s record to accounting.
- Your team
- Close and reconciliation
- Recovery
- Separate exceptions from confirmed totals and assign follow-up.
06 Records
What is confirmed and recorded.
Confirmed totals kept apart from exceptions
An unknown result stays unresolved until its status is confirmed
POS options
Start with the workflow, then choose hardware.
Order flow, checkout style, inventory, accounting, and training shape the right POS. OmniPay maps those pieces before recommending a processor or hardware path.
By operating model
Retail
- Barcode scanning
- Inventory tracking
- Multi-location stock sync
- Customer display
- Loyalty program integration
- End-of-day reporting
Restaurant
- Table management
- Split bills
- Kitchen display system (KDS)
- Tip prompts
- Menu modifiers
- Online order integration
Enterprise
- Multi-store dashboard
- Role-based staff permissions
- Custom reporting & analytics
- Integration support
- Escalation planning
Custom
- Existing hardware compatibility check
- Custom integration consultation
- Launch support
Common platforms
CloverSquareLightspeedToastMoneris
Connected-system question
Define the technical handoff