| Anchor | ||
|---|---|---|
|
Preface:
Chowly is a third party software company that we integrate with which allows us to push and pull menus from and push orders from to a restaurant’s POS system. We’ve been set up for a while now on ChowlyV1 and have now begun moving to ChowlyV2. Chowly V1 is no longer relevant.
...
What POSs are supported by Chowly?
...
TOAST
...
SQUARE
...
CLOVER
...
UPSERVE
...
REVEL
...
BRINK
...
ALOHA - complicated system that has a different process then described below
...
arrow pos
breadcrumb/upserve
par brink
clover
hot sauce
GemPOS
Kyoo
lightspeed(L series/U series)
Link POS
Microsale
OrdyX
Revel
Rezku
ServingIntel
Selflane
square
Toast
Aloha (takes a bit longer due to their complicated system)
Who is the point of contact for the RDS & restaurant?
...
If a restaurant has a previous chowly account that has terms/service, it is unrelated to any new account that is activated for their integration with DeliverLogic RDSs.
The restaurant must continue to stay current/paying fees on the first account (if they have one) with other 3rd party delivery services integrated.
The restaurant will not be paying on the second account because the RDS takes on the charges.
The RDS can pass on the monthly fee if they so choose, but it does not happen automatically.
What charges are actually being charged?
Chowly 1.0 - no new customers are being added to this. Updates were made, and moving forward, any new restaurants are automatically going to be 2.0
Chowly 2.0
Install fee is waived if already on Chowly 1.0
$50 install fee (RDS Charge is collected when submitting the POS integration request form)
$.39 an order (RDS Charge) up to $35/per month per restaurantwith a $39 monthly minimum per merchant location.
Are there ever instances where orders don’t flow through properly to the restaurant?
Yes, sometimes during software updates orders don’t flow through.
To resolve an issue as quickly as possible when this occurs we need:
RDS Name
RDS Location
Restaurant Name
Order Number
...
Deliver Logic reviews the backend and determines what the error messages are.
If necessary, you may need to call in the order to the restaurant so they can get it started (we can have our dispatch service center do this for you as well)
DeliverLogic will work on correcting the error as fast as possible and inform the RDS when it is fixed
...
Restaurant and/or RDS jotform for POS Integration request (correct contact info a must)
RDS Owner must inform the restaurant owner that a call + email from Chowly is coming within the next week and to be on the lookout for it.
Julie receives and reviews (follow up if incomplete)
Julie forwards the The restaurant info is forwarded to the Chowly team
Chowly team will make initial contact with the restaurant to fill them in on what is needed within their POS. This is a 15-20 min call with restaurant covering entire integration process
Make sure menu is correct in the POS
Go over screens and printers
They can help but takes extra time to be done - it is best for the restaurant to do this themselves
The restaurant might have “home work” in organizing and cleaning up their menu inside their POS
Chowly will schedule another call between the restaurant and the Chowly implementation team for the actual integration
Chowly implementation calls are on Wednesdays and Thursdays.
Call covers syncing of menus and testing orders.
Julie DeliverLogic will TRY to send test orders the same day as this Chowly call, usually between 2p-4plunch and dinner service, otherwise it will be the following day.
Troubleshooting occurs during this call to correct any errors.
Once test orders are completed successfully, the POS Integration is complete.
Julie or other support agents will reach out to the RDS own to notify them of the completed integration.
The main point of contact becomes Deliver Logic DeliverLogic once integration is completed.
Juliette Reyes on Slack
juliette@deliverlogic.com for email
...