HubSpot–Acumatica Sync for Personal Care Brands Selling to Salons and Retailers

What this looks like in personal care

A salon group has a central payer, individual locations, and stylists requesting testers. Sales sees people and opportunities, while finance needs a stable customer hierarchy. Automatically creating a customer for each stylist would duplicate accounts and confuse which location can order under the group’s terms.

Records, ownership, and update rules

Work through the process

1. 01
   Review the account hierarchy

   List legal payer, salon locations, buyers, and independent professionals separately. Agree which level owns an opportunity, sample request, and paid order.
2. 02
   Inspect the ERP contract

   Confirm the available customer and location entities and any custom fields with the Acumatica administrator. Connector availability does not establish every tenant-specific field or action.
3. 03
   Protect finance fields

   Share approved customer context with sales while treating proposed legal or terms changes as review requests. Do not let an ordinary CRM edit silently become a finance decision.
4. 04
   Exercise new locations

   Test adding a salon under an existing payer and moving a buyer between locations. Verify that historical orders retain the original customer and destination references.
5. 05
   Add a stylist contact in HubSpot and watch what Acumatica does

   Create a HubSpot contact for a stylist who rents a chair at an existing salon customer and flag them as a tester requester. Then open the Acumatica customer list. No new customer should appear; the contact sits under the salon company with the payer question left open for finance. A fresh Acumatica customer created from that contact stops the rollout until the create permission is removed from the mapping. Next, move an existing buyer to a second location in HubSpot and reopen their earlier sales orders in Acumatica. Those orders must still show the original ship-to and payer. Rewritten history means location changes are overwriting rather than versioning.

Handle the exceptions explicitly

Independent stylist rents space

Confirm whether the stylist or salon is the actual payer before mapping the account.

Salon group acquires a location

Review legal and location relationships rather than merging history by brand name.

ERP entity is customized

Scope the specific endpoint fields and operations before enabling writes.

What to verify before expanding

• A tester contact cannot automatically become a duplicate legal customer.
• Location changes preserve prior order and payer relationships.
• An independent stylist and the salon sharing a site retain distinct payer candidates until the actual buyer is confirmed.
• A salon acquisition triggers legal-customer review without automatically moving prior orders to the acquiring group's account.

Technical references

• Stacksync two-way sync quick start