Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 20 Next »

⚙️ Vendor Configs

Last update:

The current vendor configs setup has the following fields: rPOS, rPOS Delivery, SimplyDelivery Tablet, SimplyDelivery Tablet Delivery, Tablet, Tablet Delivery, Partner and Partner Delivery.

image-20240209-131847.png

  • rPOS fields: those fields we’re added to enable the direct integration between our platform and rPOS. Given that we’re no longer pursuing an integration with rPOS, we aren’t using these fields anymore.

We will be removing the rPOS fields to declutter and simplify the UI.

  • Tablet fields: these are legacy fields which we planned to use for SimplyDelivery at the beginning of the project. We aren’t using these fields anymore.

We will be removing the Tablet fields to declutter and simplify the UI.

  • SimplyDelivery Tablet fields: these fields are used for the SimplyDelivery order payload. Currently we only have Delivery enabled (Simply Delivery Tablet Delivery field), although Pick Up might be enabled in the future (Simply Delivery Tablet).

    • However, SIDES does not perform a PLU check on items we’re sending – that’s because we’re not sending the order directly to the POS, but instead sending it to the SIDES’ tablet. Therefore, SIDES will generally accept items as long as they have a name and a price. 

    • That’s why all the SimplyDelivery PLUs are set to match the Sanity ID (which is a long alphanumeric code – e.g. 75e80b14-5548-4a39-8bc2-3267450feb61) as a Constant PLU. 

    • So SIDES does not ‘care’ about the PLU we’re sending and the actual value of the PLU is not relevant to them.

However, the PLU type (whether it is a Constant PLU, Ignore, etc) matters for SIDES. That’s because SIDES checks whether the sum of the item prices in an order match with the total order price. When an item’s VendorConfig is set to Ignore in Sanity, our platform assumes it’s priced at 0. 

Whenever an order is placed with an item that has its PLU set to Ignore, the order total sent to SIDES is different to the sum of all the item’s prices. Hence, SIDES will automatically cancel orders with the message diffecence between payments and overall sum detected.

Note that SIDES and Simply Delivery are the same company.

  • Partner fields: the Partner fields will be used for POS integrations via our Partner API. They will store the Pick Up and Delivery PLUs for Oracle POS.

Note that in the past we were using the Partner fields to input Toshiba PLUs for offers and rewards. We have now created a new Toshiba Loyalty field for that purpose, see below.

  • Toshiba Loyalty field: this field will be used to input the Toshiba PLUs which Toshiba, Acrelec and Tillster use as part of the Loyalty integration.

The Digital Operation Portal (DOP) is used to manage availability & pricing. Sanity and the DOP must be used in conjunction and teams using each tool must coordinate for any new launches or menu changes.

  • E.g. Small menus need to be set as unavailable in the DOP. Sanity PLU configuration should not be used to manage availability.

🔍 Root cause analysis on product launch (07th March)

Problem

BK DE has experienced a delay to make new products (HD BoGof) available on the App:

  • Long Chicken® 2 for 1

  • Plant-based Long Chicken® 2 für 1

After publish the Sanity document multiple times, the product was still not available on the App.

Root cause analysis

  1. Based on our instructions, BK DE setup the PLUs as constant PLU under Vendor Configs:

    1. SimplyDelivery Tablet fields:

      1. SimplyDelivery Tablet

      2. SimplyDelivery Tablet Delivery

    2. Partner field set to Ignore;

  2. BK DE reviewed the vendor configuration and didn’t find any error and the ticket was submitted IREQ-1743 - Getting issue details... STATUS on Tech Support.

  3. BK DE decided to delete the current Sanity document and re-created the documents with the same vendor config setup and the products were available on the App.

  4. Sanity cache issue may cause the issue on products were not available on a short period of time.

    1. After re-create a new Sanity document, the App took into consideration the new Document_ID.

Steps for solution

  1. Address Sanity cache issue to engineer team start investigation: https://rbictg.atlassian.net/jira/servicedesk/projects/IREQ/queues/issue/IREQ-1859

  • No labels