Anchor
​

Preface:
Chowly is a third party software company that we integrate with which allows us to pull menus from and push orders 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.

Chowly V2 allows DL to pull the menus from the restaurant’s POS system and sync them into RDSLogic.  V1 allowed for the sending of orders from RDSLogic through Chowly to the restaurant’s POS system via a parsing map, but did not allow for menu pulling.  V2 allows for menu pulling and sending of the order via API to the restaurant’s POS system. This eliminates the need for manual menu set-up.

Here is the form to submit a POS integration request for a restaurant: https://form.jotform.com/93005564956160



What POSs are supported by Chowly?

  • 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? 


Some customers already have an account with Chowly. Which account do they use?

  • 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

    • $50 install fee (RDS Charge is collected when submitting the POS integration request form) 

    • $.39 an order (RDS Charge) with 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

Slack is the fastest way to send us the info

  • 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 



**Very important the restaurant has their menu setup properly in the POS**



Things to double check on the restaurant end:



  • Menu is laid out within the POS the way they would like it displayed on the RDSs site

    • NESTED MODIFIERS ARE NOT SUPPORTED BY CHOWLY - THESE NEED TO BE RE-WORKED IF THE RESTAURANT HAS ANY

  • Times are adjusted to reflect desired availability for lunch/dinner items, brunch, specials, etc…

    • There are specific settings for each type of POS, Chowly SHOULD help the restaurant set things up correctly on one of the scheduled calls they will make with the restaurant owner/manager

  • Devices are set up to “auto-fire” (Toast POS Only)

    • “autofire only needs to be enabled on one device. doesn’t really matter which device. if they have it on and orders are still not printing, then they need to confirm that the dining options are enabled. if they go to that kitchen screen, go to settings, then device setup, then ticket display options. they’ll see the RDS dining options there. they need to make sure the boxes are checked”

  • Other printer settings are checks and confirmed to be going the the right place


POS Integration Timeline:

  • 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)

  • 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.

    • DeliverLogic will TRY to send test orders the same day as this Chowly call, usually between lunch 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 DeliverLogic once integration is completed.



  • Once integration is complete, Automated menu updates are synced every time there is a change (happens overnight around 2am)