Database Administrators, Technical Teams, Project Managers, Product Managers
It is helpful to know what the high level journey of data is in specific scenarios. This article is meant to give that basic understanding.
1. The database that is managed in Configuration Center is communicated to the Catalog, which is in the cloud. This Catalog data is communicated through NCR's Business Services Platform and is shared out to API partners upon request.
2. Olo makes requests per vendor (store) to the Catalog via BSP to get pricing that is ultimately displayed on the web site/app for the store. This data is also used in Olo's mapping tools. When the data comes back from the Catalog, there are inconsistencies that can cause what Olo terms "mismatches":
- No pricing for the items/mods in the Catalog response (not $0 pricing, but literal blank/no pricing) results in a mismatch.
- Mapped IDs that are not found in the Catalog response result in a mismatch.
3. The Order journey is depicted in the below flowchart. This is symbolic of a very basic order with either a payment or as pay in store. There are different permutations including loyalty, discounts, split payment, etc. This is intended to only give a high level understanding. Important factors worth mentioning are:
- The Catalog data mentioned in Solution 2 above is determined by what is mentioned in Solution 1 above.
- The Catalog data determines what pricing is shown (sticker pricing) on the site.
- The Validation call (Calculate Tax + Total or CTT) returns POS controlled final taxation and final pricing.
- The Commit is the final step after payment is applied by the guest and the order is sent by Olo to BSP.
- All printing in the local POS system is controlled by POS configuration rules.