共用方式為

Integrate AiFi to Dynamics 365 Commerce connector (preview)

  • 發行項

Important

Some or all of this functionality is available as part of a preview release. The content and the functionality are subject to change.

This article provides an overview of the integration process for the AiFi to Dynamics 365 Commerce connector (preview) in Microsoft Cloud for Retail.

Integrate product master data

You need to push assortments to AiFi for product master data updates and set the batch job frequency. Batch jobs related to master data ensure products are synced seamlessly with AiFi.

The following product details are transferred between Dynamics 365 Commerce and AiFi:

  • Product ID
  • Product name
  • Default variant on the product (if applicable)
  • Barcode of default variant (if applicable)
  • Product variant name (if applicable)
  • Product variant bar code (if applicable)

In addition to the one-time data sync, the connector also ensures that any incremental updates are synced to AiFi. For example, if any field on a product is updated, the modified product record is synced again with AiFi to maintain data consistency.

Important

The connector treats Dynamics 365 Commerce as the master source of data. Therefore, any updates made directly in AiFi won't be synchronized back to Dynamics 365 Commerce..

Integrate value for customer transactions

When a customer enters a store powered by the AiFi frictionless solution, their interactions with products are captured via camera. These details are then collated and transferred to the Commerce-AiFi connector via webhooks. The connector processes this raw data to create a transaction in Commerce CSU and apply real-time pricing.

The following customer transaction details are transferred from AiFi:

  • Customer ID: The external ID maintained on the AiFi side.

  • Product ID: The IDs of products that the customer bought.

  • Store ID: The store where the customer completed the transaction.

  • Customer metadata:

    The supporting data transferred from AiFi includes additional data points related to the transaction or customer, such as compliance requirements from the payment service provider. Metadata fields can be used to meet specific requirements from payment service providers. In this scenario, the Commerce connector acts as a conduit, meaning the fields need to be transferred through the capturing solution (AiFi). The following fields are currently available:

    • expirationDate: Card expiration date
    • networkTransactionID: The transaction ID of the network
    • For unknown customers: Used to identify if the person who transacted is a known customer or not.
    • isKnownCustomer: If the person is a known customer, that is, the customer ID exists, then the transaction is posted against the specific account; otherwise, it's posted against the default customer account set at the organization level.

    Additionally, the connector transfers the details to the Commerce at runtime, where custom code from the customer retrieves the information to be sent to the respective payment service provider. After the payment is processed, the transaction is completed.

  • Receipt:

    A receipt is generated using the default functionality in Dynamics 365 Commerce, which can then be sent to the customer via the out-of-box email setup in Commerce or via any third-party service through custom integration.

    • Only the transactions that have product-related financial movements, that is, someone taking the products out, are the ones that are created in Commerce.

    • The receipt ID is of format MMDDYY-1##########, here MMDDYYY refers to MonthDateYear and the numbers ########## refer to the ID of order provided by AiFi.

The connector provides assurance through a combination of automated and batch-based retry mechanisms:

  • Automated retry: An instant retry if, for some reason, the transaction doesn't get processed the first time due to system unavailability, network congestion, or any other issue.

  • Periodic retry: Commerce connector comes with an out-of-box batch job that can be configured to ensure periodic retries for the past one week of failed transactions.

    Important

    AiFi to Dynamics 365 Commerce connector (preview) requires registration and is currently only available to approved customers and partners during the preview period. Request configuration support to AiFi to Dynamics 365 Commerce connector (preview) during the preview period by completing the AiFi to Dynamics 365 Commerce connector (preview) sign-up form.