Summary
Comparison of Redcat online ordering and 3rd party integrated ordering platforms and how they need to be managed & interact with the Redcat platform.
Contents
SmartOrder Processor Status
Take Store Offline
Adjust Prices
Make Items Unavailable
Customer Receipt
Reprint Production Docket
Adjust Trading Hours
Customer Refunds
Order Lead Time
SmartOrder Processor Status
| Redcat Online Ordering | Orders cannot be finalised via Redcat Online Ordering, if SmartOrder Processor status is Offline or Unknown. |
| Google Food Ordering Integration | Orders cannot be finalised via Redcat Online Ordering, if SmartOrder Processor status is Offline or Unknown. |
| Uber Eats Integration |
Orders will still attempt to integrate but will fail if SmartOrder Processor status is Offline or Unknown. Failed orders will show on the Uber Eats tablet. Orders which fail integration will need be entered manually into the POS. |
| DoorDash Integration |
Orders will still attempt to integrate but will fail if SmartOrder Processor status is Offline or Unknown. Failed orders will show on the DoorDash tablet or in the DoorDash Merchant Portal. Orders which fail integration will need to be entered manually into the POS. |
| Deliveroo Integration |
Orders will still attempt to integrate but will fail if SmartOrder Processor status is Offline or Unknown. Failed orders will show on the Deliveroo tablet. Orders which fail integration will need to be entered manually into the POS. |
| Just Eat [Menulog] Integration |
Orders will still attempt to integrate but will fail if SmartOrder Processor status is Offline or Unknown. Failed orders will show on the Menulog tablet. Orders which fail integration will need to be entered manually into the POS. |
| TabSquare Integration |
Orders will still attempt to integrate but will fail if SmartOrder Processor status is Offline or Unknown. Orders which fail integration will be indicated to the client via TabSquare Console; console.tabsquare.com. |
Take Store Offline
| Redcat Online Ordering |
Legacy POS: Manage Web Orders | Manage Store Status | Launch 3rd Party Control Console Polygon POS: NOTE: HQ setup determines if the store has access to this function. |
| Google Food Ordering Integration |
Legacy POS: Manage Web Orders | Manage Store Status | Launch 3rd Party Control Console Polygon POS: NOTE: HQ setup determines if the store has access to this function. |
| Uber Eats Integration |
Legacy POS: Manage Web Orders | Manage Store Status | Launch 3rd Party Control Console Polygon POS: NOTE: HQ setup determines if the store has access to this function. |
| DoorDash Integration |
Legacy POS: Manage Web Orders | Manage Store Status | Launch 3rd Party Control Console Polygon POS: NOTE: HQ setup determines if the store has access to this function. |
| Deliveroo Integration |
Legacy POS: Manage Web Orders | Manage Store Status | Launch 3rd Party Control Console Polygon POS: NOTE: HQ setup determines if the store has access to this function. |
| Just Eat [Menulog] Integration |
Via the Menulog tablet or Partner Centre. |
| TabSquare Integration | Can be done via TabSquare Kiosk or TabSquare CMS; cms.tabsquare.com |
Adjust Prices
| Redcat Online Ordering |
Update relevant Price Level for Redcat Online Ordering in Redcat BOH and publish to Polygon Central. Ensure that update is also sent and downloaded on POS terminals. |
| Google Food Ordering Integration |
Update relevant Price Level for Google in Redcat BOH and publish to Polygon Central. NOTE: changes may take up to 1 hour to be reflected on Google. Ensure that update is also sent and downloaded on POS terminals. |
| Uber Eats Integration |
Update relevant Price Level for Uber Eats in Redcat BOH, publish to Polygon Central and complete Uber Eats menu export – ideally outside normal trading hours. Ensure that update is also sent and downloaded on POS terminals. |
| DoorDash Integration |
Update relevant Price Level for DoorDash in Redcat BOH, publish to Polygon Central and complete DoorDash menu export – ideally outside normal trading hours. Ensure that update is also sent and downloaded on POS terminals. |
| Deliveroo Integration |
Update relevant Price Level for Deliveroo in Redcat BOH, publish to Polygon Central and complete Deliveroo menu export – ideally outside normal trading hours. Ensure that update is also sent and downloaded on POS terminals. |
| Just Eat [Menulog] Integration |
Update relevant Price Level for Menulog in Redcat BOH, publish to Polygon Central and complete Menulog menu export – ideally outside normal trading hours. Ensure that update is also sent and downloaded on POS terminals. |
| TabSquare Integration | Update relevant Price Level for TabSquare in Redcat BOH, publish to Polygon Central and complete TabSquare menu export – ideally outside normal trading hours. Then perform a menu sync at TabSquare CMS; cms.tabsquare.com |
Make Items Unavailable
| Redcat Online Ordering | Manage via Web Orders button at POS or in Polygon Central. |
| Google Food Ordering Integration | Manage via Web Orders button at POS or in Polygon Central. |
| Uber Eats Integration | Manage via Web Orders button at POS or in Polygon Central. |
| DoorDash Integration | Manage via Web Orders button at POS or in Polygon Central. . |
| Deliveroo Integration | Manage via Web Orders button at POS or in Polygon Central. |
| Just Eat [Menulog] Integration |
This can be done in the Menulog Partner Centre. |
| TabSquare Integration |
Can be done via TabSquare Kiosk or TabSquare CMS; cms.tabsquare.com |
Customer Receipt
| Redcat Online Ordering |
Customer receipt is emailed to the customer. Receipt can be reprinted at POS via Sales History. |
| Google Food Ordering Integration |
Customer receipt is emailed to the customer. Receipt can be reprinted at POS via Sales History. |
| Uber Eats Integration |
Customer receipt via Uber Eats. NOTE: Receipt printed at POS does not include Uber Eats Delivery Fee |
| DoorDash Integration |
Customer Receipt via DoorDash. NOTE: Receipt printed at POS does not include DoorDash Delivery Fee. |
| Deliveroo Integration |
Customer Receipt via Deliveroo. NOTE: Receipt printed at POS does not include Deliveroo Delivery Fee |
| Just Eat [Menulog] Integration |
Customer Receipt via Menulog. NOTE: Receipt printed at POS does not include Menulog Delivery Fee. |
| TabSquare Integration |
Customer receipt is printed once at the TabSquare Kiosk. Receipt can be reprinted at POS via Sales History. |
Reprint Production Docket
| Redcat Online Ordering | Recall | Zoom Sale |
| Google Food Ordering Integration | Recall | Zoom Sale |
| Uber Eats Integration | Recall | Zoom Sale |
| DoorDash Integration | Recall | Zoom Sale |
| Deliveroo Integration | Recall | Zoom Sale |
| Just Eat [Menulog] Integration |
Recall | Zoom Sale |
| TabSquare Integration | Recall | Zoom Sale |
Adjust Trading Hours
| Redcat Online Ordering |
Standard Trading Hours: Configure in Redcat BOH at HQ level, push out via polygon central & POS Updates. Custom Trading Hours: Can be configured using our ‘Custom Trading Hours’ option in Polygon Central. |
| Google Food Ordering Integration |
Standard Trading Hours: Configure in Redcat BOH at HQ level, push out via polygon central & POS Updates. Custom Trading Hours: Can be configured using our ‘Custom Trading Hours’ option in Polygon Central. NOTE: Changes may take up to 1 hour after the Web Menu is published. |
| Uber Eats Integration |
Standard Trading Hours: Configure in Redcat BOH at HQ level, publish to Polygon Central and complete Uber Eats menu export. See notes in Adjust Trading Hours section. Custom Trading Hours: Can be configured directly in Uber Eats Restaurant Dashboard/tablet. |
| DoorDash Integration |
Standard Trading Hours: Configure in Redcat BOH at HQ level, publish to Polygon Central and complete DoorDash menu export. Custom Trading Hours: Can be configured using our ‘Custom Trading Hours’ option in Polygon Central. DoorDash menu export will need to be sent after changes are made. |
| Deliveroo Integration |
Standard Trading Hours: Must arrange trading hours changes directly with Deliveroo. Custom Trading Hours: Must arrange trading hours changes directly with Deliveroo. NOTE: If hours do not match, a Deliveroo order placed outside Redcat trading hours will not attempt integration. |
| Just Eat [Menulog] Integration |
Standard Trading Hours: Configure in Redcat BOH at HQ level, publish to Polygon Central and complete Menulog menu export. Custom Trading Hours: Contact Menulog to arrange custom trading time. |
| TabSquare Integration |
Must be done via TabSquare CMS. cms.tabsquare.com |
Customer Refunds
| Redcat Online Ordering |
Refunds to customers need to occur via the Stripe account connected to that location. If possible, the sale should also be cleared at POS so that payments & transactions can be reconciled. |
| Google Food Ordering Integration |
Refunds to customers need to occur via the Stripe account connected to that location. If possible, the sale should also be cleared at POS so that payments & transactions can be reconciled. |
| Uber Eats Integration |
Contact Uber Eats for refund process. If possible, the sale should also be cleared at POS so that payments & transactions can be reconciled. |
| DoorDash Integration |
Contact DoorDash for refund process. If possible, the sale should also be cleared at POS so that payments & transactions can be reconciled. |
| Deliveroo Integration |
Contact Deliveroo for refund process. If possible, the sale should also be cleared at POS so that payments & transactions can be reconciled. |
| Just Eat [Menulog] Integration |
Contact Menulog for refund process. If possible, the sale should also be cleared at POS so that payments & transactions can be reconciled. |
| TabSquare Integration |
Partial or Full refund can be processed via TabSquare Console; console.tabsquare.com If possible, the sale should also be cleared at POS so that payments & transactions can be reconciled. |
Order Lead Time
| Redcat Online Ordering |
Default Value: Order Lead Time Rules: view documentation |
| Google Food Ordering Integration |
Default Value: |
| Uber Eats Integration | Uber Eats have their own algorithm which applies – changes made in Polygon POS Management will NOT affect the Uber Eats lead time. |
| DoorDash Integration | DoorDash uses their own algorithm to estimate pickup time when creating the order, but this is overwritten with the average order prep time included with the confirmation from Redcat – therefore adjustments as per the Redcat Online Ordering column applies. |
| Deliveroo Integration | Deliveroo have their own algorithm which applies – changes made in Polygon POS Management will NOT affect the Deliveroo lead time. |
| Just Eat [Menulog] Integration |
Menulog have their own algorithm which applies – changes made in Redcat will not affect the Menulog lead time. Contact Menulog to have this adjusted. |
| TabSquare Integration | As this is an on-premises ordering platform (Kiosk/Table Ordering), no Average Order Prep Time is required for TabSquare |