NUTRINTG Shopify reorder - rejected

1

User checks whether wants reorder

• There are two additional fields in the check-out view in Shopify

  • check-box: "true" (string) if the customer wants to reorder

  • Frequency: predefined terms of possible reorder (example: 5, 10, 15, 30, 45, 60 days)

2.

Shopify back-end save the custom value

• "note_attributes": [ {"reorder":
{
"reorder_check": "true"/"false", "frequency": "45"
} } ]

  Note_attributes are extra information that is added to the order. Appears in the Additional details section of an order details page. Each array entry must contain a hash with name and value keys.

• This is no longer valid, reoder service will determine if requets are applicable based on shopify domain. Whole domains will be enrolled for the roerder functionality. 

• Frequency will be stored together with shopify domain.

3.

Middleware order service

• Shopify to CDP Integration

• Test endpoint:  http://cdp-shopify-order-service.de-c1.cloudhub.io/webhook/shopify

4.

Anypoint Exchange

• Duplicate message and send to the Clients' (Reorder service, Order Adapter) queues

• Clients: 

  • Order Adapter

  • Reorder service

5.

Order Adapter flow

• Take requests from the queue and proceed to create csv files

6.

MW Re-Order service

• Take requests from the queue

• Order service checks for "reorder_check" value (true/false)

• In case:

  • "reorder" : "false".   Shopify domain is not enrolled for reorder

    • drop

  • "reorder" : "true"    Shopify domain is enrolled for reorder

    • proceed

• Shopify domains and their frequencies are stored in mongo collection cdpReorderService_shopifyDomains: example document look like this:

  • {
    "_id" : "durex-uk-test-store.myshopify.com",
    "frequency" : "45"
    }

7. 

Call GetIndividualId service

• New service should be created for getting individual of the customer

• REST

• Endpoint:

• Authorization:

• IndividualId value is retrieved from CDP by "Get Profiles (Search)" CDP API method

• In case no account is found, the data has to be sent to Salesforce with other event ID and with email as ContactKey.

8.

Extracting relevant fields and values

• Extract:
  
  

  • email

  • order_id

  • created_at

  • shipping_address

    • address1

    • address2

    • phone

    • city

    • zip

  • first_name

  • last_name

  • Accepts marketing from customer object ("customer": { "id": 115310627314723954, "email": "john@test.com", "accepts_marketing": false)

  • For each line_item:

    • variant_id

    • quantity

    • price

• Example order webhook JSON:

Example order webhook JSON

9.

Create a reorder cart URL

• The link should be created according to the below specification:

  •  

    • The Shopify domain | example: http://your-store.myshopify.com

    • /cart/

    • variantID:quantity (first product) | example: 70881412:1

    • variantID:quantity (second product) | example: 70881382:1

  
  
  

  • other prefilled values:

    • checkout[email]

    • checkout[shipping_address][first_name]

    • checkout[shipping_address][last_name]

    • checkout[shipping_address][address1]

    • checkout[shipping_address][address2]

    • checkout[shipping_address][city]

    • checkout[shipping_address][zip]

• Example URL for a link with prefilled email and city parameters:

http://your-store.myshopify.com/cart/70881412:1,70881382:1?checkout[email]=somebody@store.com&checkout[shipping_address][city]=thisismyhometown

• Log: order_id, timestamp, reorder_URL

More info: https://help.shopify.com/en/themes/customization/cart/use-permalinks-to-preload-cart

10.

Check for relevant Event Definition Key

• In MongoDB there is a mapping: domain : Event Definition Key (to be confirmed with SF team)

• Relevant Event Definition Key is extracted

11.

Consolidate the body of the request sent to SFMC

The body request includes:

example request

• Event Definition Key for test purposes: APIEvent-4b6fd87d-cef9-4e0d-f802-cadff42bb637

12.

Pass prepared body request to the "send to SFMC service"

13.

Send to SFMC service

• Service should be REST

• Endpoint:

• Authorization:

• New service should be created

• Service authorize itself in the SFMC

• Service sends the request to the SFMC

  
  
  

  example request

  Host: https://mc1plnsfxggrfg-l69pj913rd1x4.rest.marketingcloudapis.com/interaction/v1/events Headers: Authorization: Bearer #[flowVars.accessToken] Body: {}