Child pages
  • Shopify/ACUMEN Documentation

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

                                                  vi.     ACUMEN API Site ID


 

How ACUMEN matches Shopify orders with existing customers in ACUMEN:

  • First priority is the <PartyACUMENID>, the contents of which are used to search ACUMEN Customer ID's for a match.  Used for PW B2B sites, where the site knows the ACUMEN customer ID.  Few, if any, consumer sites will know/have the related ACUMEN customer ID.
  • Second priority is the <PartyID> tag.  The contents of that tag should be a unique ID from the website database for the user account.  ACUMEN prepends that ID with the ACUMEN eCommerce Site Code used to import the order and saves it with the ACUMEN Customer record as what ACUMEN calls an Old Code.  Eg <PartyID>123456</PartyID> imported using an eCommerce site record with a site code of SHP will create an Old Code of SHP123456 and save it with the customer used by the order.
  • Third priority is based on a setting in the eCommerce site record.  It can be Name, Zip, Phone, email, or simply email.  We recommend customers use the email search, rather than name, Zip, phone, email because the latter is so exacting. So, if no existing customer is found by the first two searches, ACUMEN should be configured to search for a match by email address alone.  If a match is found, the matching customer is updated with the Old Code from the second search, so even if the customer changes their email address for a future order, it will find the correct customer in ACUMEN.  If more than one customer record in ACUMEN has matching email address, the import will create a new customer record and record in the import log messages that a probable duplicate customer was created, matching email address for customer ID's 489823 and 982734

Note:  If you want to test the connection between your ACUMEN server and the Shopify app, you can use the following instructions:

...

  1. How often Product schedule run
    1. Product schedule will run once in a day.
  2. How often Order schedule run
    1. Order schedule will run once in every hour.
  3. I see ACUMEN order id into ACUMEN integration APP but can't find order information into ACUMEN
    1. ACUMEN has to process the order information to create invoices. Go to OE/AR -> eCommerce Site and make sure the Process New Orders box is checked on the General page of the site record. Save and close the site record then click the Receive button at the bottom of the eCommerce Site record list. When the receive button is clicked, ACUMEN looks for eCommerce Order records with a status of New and then processes the order data to create invoices. This is usually done as a manual process, but it's possible to set up a computer that will scan for new eCommerce Order record and process them automatically. 
  4. How ACUMEN matches Shopify orders with existing customers in ACUMEN:

    • First priority is the <PartyACUMENID>, the contents of which are used to search ACUMEN Customer ID's for a match.  Used for PW B2B sites, where the site knows the ACUMEN customer ID.  Few, if any, consumer sites will know/have the related ACUMEN customer ID.
    • Second priority is the <PartyID> tag.  The contents of that tag should be a unique ID from the website database for the user account.  ACUMEN prepends that ID with the ACUMEN eCommerce Site Code used to import the order and saves it with the ACUMEN Customer record as what ACUMEN calls an Old Code.  Eg <PartyID>123456</PartyID> imported using an eCommerce site record with a site code of SHP will create an Old Code of SHP123456 and save it with the customer used by the order.
    • Third priority is based on a setting in the eCommerce site record.  It can be Name, Zip, Phone, email, or simply email.  We recommend customers use the email search, rather than name, Zip, phone, email because the latter is so exacting. So, if no existing customer is found by the first two searches, ACUMEN should be configured to search for a match by email address alone.  If a match is found, the matching customer is updated with the Old Code from the second search, so even if the customer changes their email address for a future order, it will find the correct customer in ACUMEN.  If more than one customer record in ACUMEN has matching email address, the import will create a new customer record and record in the import log messages that a probable duplicate customer was created, matching email address for customer ID's 489823 and 982734

Shipping Mapping Settings

...