User Guide
  • Intro
    • Welcome
      • About DotApparel
      • What is DotApparel?
      • Where is it hosted?
      • What platform(s) do we support?
      • How does syncing work?
      • Solution architecture
      • Definition of “Instance”
      • Security Overview
    • Implementation
      • Google Cloud and Firebase
  • Quick Links
  • Core
    • Overview
    • Dashboard
    • Orders
      • Mappings
      • Integrations
    • Returns
      • Mappings
    • Products
      • Mappings
        • Default mapping rules
      • Translations
      • Markets
      • Publishing products
    • Inventory
      • Mappings
        • Examples
          • Ignore Sync
          • Inventory Buffer
          • Keep Items Sold Out
          • Unlimited Inventory
    • Customers
    • Rewards
    • System Alerts
    • Settings
      • Shopify Locations, DotApparel Locations and Inventory Buffers
      • ERP credentials
      • Product images
      • Fulfillments
      • Payment gateways
      • Gift cards
      • Refunds
      • Notifications
      • Harmony Integration with DotApparel
    • Modules
      • Ship From Store
      • Local Pickup/Click & Collect
      • Shopify Markets
      • Returns
        • Australia Post (AusPost)
        • Loop Returns
      • Auto-Refunds
        • Refunding Shopify Orders from POS (In-Store)
      • Integrate with Brauz (app)
      • Integrate with The Wishlist (app)
    • Release Notes
    • Troubleshooting
      • FAQs
      • How to raise a support ticket for an issue
      • Good and bad examples of a problem ticket
      • Want to enable a new omnichannel feature?
      • Want to integrate a marketplace using DotApparel?
  • Customers
    • Overview
      • Email Examples
    • Getting Started
      • Understanding Customer Setup in your ERP
      • Data Sync
      • Configuration
      • Testing
    • Data Export Approaches
      • Option A: Consultant
      • Option B: In-House
    • Apparel21 Export Templates
    • Apparel21 Export Changelog
    • Dashboard
    • Customers
    • Orders
    • Translations
    • Mappings
    • Settings
    • Support
  • Loyalty
    • Overview
    • Getting Started
      • Terminology
    • Data Sync
      • Workflows
    • Front-End Implementation
    • Rewards Redemption
    • Rewards Emails
    • Things To Know
Powered by GitBook
On this page
  • New Loyalty Sign-Ups
  • Yotpo Tiers
  • In-store Purchases

Was this helpful?

Export as PDF
  1. Loyalty

Data Sync

High level overview of how the solution syncs data

The sync works by linking Yotpo's loyalty program with Apparel21 (POS) through the DotApparel API. This integration lets Apparel21 use Yotpo's complete loyalty program features, replacing the old Rewards module in Apparel21.

New Loyalty Sign-Ups

  • New Customers from POS: Customers can join the loyalty program when they're at the store. New customers from Apparel21 sync through to Yotpo Loyalty via DotApparel API. To make sure that new customers signing up for loyalty programs in stores experience minimal delays, we've set up a process to sync the updated customer data every minute. DotApparel Loyalty will create the customer in the connected Shopify store. This step ensures that customer data is centralised and synchronised across Apparel21, Shopify and Yotpo.

  • New Customers from Online: The Yotpo Loyalty app, integrated with Shopify, will automatically sync the newly created Shopify customer to the Yotpo loyalty program. Information automatically gets associated to the respective customer profile. This means customers can start earning and using their rewards both in the store and online.

In-store customers must be marked as WEB customers in Apparel21

To make sure the loyalty system can work with in-store customers, it's really important to label them as WEB in Apparel21. This labelling helps the loyalty system connect with them and make updates through the API.

Yotpo Tiers

We're connecting Yotpo's loyalty program with Apparel21 to combine loyalty data, like tier names, expiry dates and rewards. This gives a full picture of customers' loyalty everywhere and allows personalised service based on their achievements. Here's how we do it:

  • Setting Up a Listener: We create a special "listener" in DotApparel Loyalty that waits for a signal from Yotpo whenever a customer's loyalty tier change.

  • Getting the Update: Yotpo tells us a customer's tier changed, who they are and the tier expiry dates.

  • Updating in Apparel21: We then use the DotApparel API to tell Apparel21 to update that customer's tier level.

  • Customising in Apparel21: We decide how the loyalty info should look in Apparel21, which might mean tweaking some fields or attributes in the AP21 person record to store loyalty-related information.

Apparel21 Customer Attributes

Keep in mind that customising Apparel21 might come with specific rules and limitations. Before project kick-off we need to decide how the loyalty info should appear in Apparel21 and POS.

In-store Purchases

We're connecting the in-store order data in Apparel21 with Yotpo's loyalty program. This way, when customers shop in the store, they'll still get rewards as all of the information lands back into Yotpo Loyalty. Here's how we do it:

  • Exporting Store Purchase Data: The app grabs all the info about customers' in-store purchases from POS. This data is usually in a file that looks like a spreadsheet and includes details about your order, who you are, and what you bought. More info here.

  • Saving the Store Data: The app keeps this data in our system so we can work with it. It's like putting it on our shelf for later. The saved data is processed at the desired interval which is daily or hourly.

  • Sending Data to Yotpo: We use a special tool called the Yotpo Loyalty API to send customers' in-store purchase data to Yotpo. It's a bit like mailing a letter. Specifically, the Create Order endpoint from the Yotpo Loyalty API is used for this purpose. The app constructs the necessary request payload using the stored in-store order data and sends the request to Yotpo.

  • Making the Data Fit: Before sending it, we make sure the data looks right for Yotpo's system. It's a bit like translating it into a language Yotpo understands. All the mappings and transformations to ensure compatibility with Yotpo's API format are visible in the DotApparel Loyalty app interface.

  • Getting Your Loyalty Status: Yotpo gets the data, figures out the tier the customer should belong to based on the loyalty rules, then assigns the correct tier status to the customer's account. This means customers get rewards for their in-store shopping (not just online).

PreviousTerminologyNextWorkflows

Last updated 1 year ago

Was this helpful?