Wholesale CPG Account Onboarding: Coordinate Sales, Finance, and Operations

What this looks like in consumer packaged goods

A retailer sends a buyer contact, a trading name, and delivery instructions for three distribution centers. Sales wants the account active immediately. Finance still needs the legal payer and terms decision, while operations must identify which location is the first ship-to. Creating a customer prematurely leaves each team correcting a different version later.

Records, ownership, and update rules

Work through the process

1. 01
   Collect the minimum packet

   Request the buyer’s legal entity, billing contact, delivery locations, and intended ordering channel. Distinguish required fields from useful enrichment so the team knows which missing fact actually blocks activation.
2. 02
   Resolve duplicates before creation

   Search the existing account hierarchy using approved identifiers and human review where necessary. A new buyer contact or trading name can belong to an existing payer, so email alone is not a safe customer key.
3. 03
   Run parallel reviews with a final gate

   Finance can review terms while operations checks ship-to details. Keep both decisions visible and require their completion before the workflow marks the account ready for its first order.
4. 04
   Verify activation

   Read the accepted ERP customer reference and the CRM association. Give sales the final status and unresolved restrictions, such as a location still awaiting confirmation, rather than a vague onboarding-complete flag.
5. 05
   Onboard one retailer under a trading name and read back NetSuite

   Start an activation case for a retailer whose buyer writes under a trading name unlike the legal entity in HubSpot. Move the case through the finance and operations reviews, then open NetSuite: one customer must exist for that payer, carrying the approved legal name, terms and the alias, with no second customer for the trading name. Open the three ship-to records on that customer and confirm each traces to the location details operations reviewed, receiving constraints included. Check the HubSpot company shows the NetSuite reference and activation status. Stop the rollout if the alias produced a duplicate customer, or if a ship-to was created from unreviewed or copied details.

Handle the exceptions explicitly

Buyer uses a different trading name

Keep the alias while confirming the legal payer before creating another customer.

One location is incomplete

Allow only the approved locations under the chosen policy; do not copy another site’s delivery instructions.

Terms change after approval

Return that decision to finance and preserve the prior approved version.

What to verify before expanding

• An active account has a confirmed legal payer and ERP reference.
• Every approved ship-to is traceable to the reviewed location details.
• A trading-name alias resolves to the approved legal payer without creating a second ERP customer.
• An incomplete ship-to remains blocked while separately approved locations retain their own receiving instructions.

Technical references

• Stacksync Workflows quick start
• Stacksync NetSuite supported objects