B2B customer master data is the approved record of who a wholesale customer is and how the business should trade with them. For a brand or distributor, that record influences every downstream step: who can order, what they see, where goods go, which currency and price list applies, and how an invoice is issued.
When retailer account information lives across spreadsheets, inboxes and accounting software, small discrepancies become operational problems. A buyer may be connected to the wrong delivery location, a new legal entity may inherit an old price list, or finance may invoice details that sales has already changed elsewhere. The answer is not simply collecting more data. It is agreeing on the minimum reliable record, assigning ownership, and making updates follow a controlled path.
What is B2B customer master data?
B2B customer master data is the durable, approved information that identifies a business customer and defines the rules for trading with that customer. In wholesale, the customer may be a retailer, a distributor, a buying group, or another commercial legal entity.
A customer master record is different from an order. An order captures a particular transaction; master data provides the account context that should normally carry from one transaction to the next. It is also different from a CRM lead: a prospect can be incomplete, while an approved trading account needs sufficient information for ordering, fulfilment and invoicing.
Good customer master data management gives teams one shared answer to practical questions:
- Which legal entity is buying from us?
- Which stores or warehouses can receive this account's deliveries?
- Who can place orders, who receives invoices, and who owns the commercial relationship?
- Which currency, payment terms, price list and customer-specific pricing rules apply?
- Is the account approved to trade, pending review, paused or closed?
A neatly organised card file connected to a delivery box and invoice by flowing lines
Which fields should a wholesale retailer record contain?
A wholesale retailer record should contain enough information to identify the customer, execute an order and invoice correctly—without turning the record into an unstructured notes archive.
The table below is a practical baseline. The exact fields should reflect your sales model, markets and accounting process.
| Data group | Core fields | Why it matters |
|---|---|---|
| Account identity | Account name, internal customer ID, account status, retailer or distributor type | Prevents duplicate accounts and makes eligibility visible. |
| Legal entity | Registered legal name, company registration number, VAT identification number, registered country | Identifies the contracting and invoiced business. |
| Addresses | Billing address, delivery address, delivery instructions, multiple delivery locations where needed | Keeps invoices and shipments directed to the right place. |
| Contacts | Accounts payable contact, buyer or purchasing contact, sales contact, operational contacts | Sends each communication to the person responsible for it. |
| Commercial rules | Currency, price list, customer-specific pricing rules, payment terms, ordering permissions | Applies agreed trading conditions consistently. |
| Operational context | Territory, assigned account manager, shipping preferences, order notes | Helps sales and operations handle the account appropriately. |
| Governance | Data owner, approval status, last review date, change history | Shows who is accountable and whether data can be relied upon. |
Avoid relying on a free-text field called “customer notes” for essential rules. Notes are useful for context, but they are hard to validate, search and pass consistently into ordering or invoicing workflows. If a rule affects a recurring process, it should usually have its own structured field.
A unique internal customer ID is particularly useful. Names change, spellings vary and group structures can be complicated. A stable identifier gives sales, operations, finance and connected systems a dependable reference point.
For a closer look at the commercial side of the record, see this guide to customer-specific pricing in wholesale.
How should legal entities, billing addresses and delivery locations be stored?
Store the legal entity, billing address and delivery locations separately because they answer different business questions.
The legal entity is the company that enters the trading relationship and appears on contractual and invoice records. Its legal name, company registration number and VAT identification number should be associated with that entity rather than copied loosely into individual orders.
The billing address is where invoice correspondence is directed. It may match the legal entity's registered address, but it should not be assumed to do so.
A delivery address is where physical goods should be sent. A retailer might have several delivery locations: shops, a central warehouse, a third-party logistics facility or temporary event locations. Each location should be a separate, selectable record under the customer account, with its own status and delivery instructions.
This structure prevents a common wholesale mistake: treating one account name as proof that every transaction should use the same address. It also lets an authorised buyer select the right delivery location during ordering without changing the customer’s master legal details.
Use simple relationship rules:
- One legal entity can have one or more ordering accounts where the commercial model requires it.
- One account can have one billing address and multiple approved delivery locations.
- A delivery location can be activated, edited or retired without overwriting prior order history.
- Changes to the legal entity should trigger a review, not be treated as an ordinary address update.
One central company building connected to several distinct warehouse and shop delivery points
What VAT and currency data does a B2B customer record need?
A B2B customer record needs the data required to apply your own documented VAT and currency process consistently. At minimum, this commonly includes the customer’s legal country, billing country, delivery country or countries, VAT identification number, and the currency used for the account or price list.
A VAT identification number is an identifier used for VAT purposes. For relevant EU cross-border business transactions, teams can check whether a supplied EU VAT number is valid through the European Commission’s VIES VAT number validation service. [1] A check is a useful control, but it does not replace reviewing the full transaction facts, supporting evidence and applicable tax treatment.
Keep VAT-related information structured and dated where possible. For example, record when a VAT number was provided or checked, who performed the check, and whether the account needs further review. Do not let a sales contact’s email signature become the only place this information exists.
Currency is the monetary unit assigned to a customer’s commercial relationship or price list. Set an explicit account currency or define the conditions under which the account may order in more than one currency. Store the currency consistently in every system that needs it, rather than depending on symbols or free-text labels.
Currency and pricing are linked but not identical. A retailer can have a price list in a given currency, while customer-specific pricing rules can determine exceptions by product, assortment, territory or agreed commercial terms. Any change to either should be approved by the person responsible for pricing policy.
For more context on the operational side, read our guide to EU VAT compliance for B2B wholesale. VAT treatment can depend on the transaction, so obtain appropriate tax advice for your circumstances.
How should wholesale teams manage contacts, roles and approval status?
Wholesale teams should store people as contacts with defined roles, not as a single generic “customer contact.” One person may have multiple roles, and one role may have multiple people.
Useful roles include:
- Buyer or purchasing contact: selects products, raises orders or coordinates replenishment.
- Accounts payable contact: receives invoices, statements and payment-related communication.
- Sales contact: owns the commercial relationship on the supplier side, such as an account manager.
- Receiving or operations contact: handles delivery questions, booking requirements and discrepancies.
- Account administrator: is authorised to manage user access or account details in a B2B storefront.
An approval status tells teams whether the account is permitted to take a particular action. Typical statuses include prospect, pending review, approved to order, on hold and closed. Define what each status means in practice. For example, “approved” might permit ordering but not permit a buyer to alter payment terms or add a new delivery address without review.
Contact-person data needs care. Limit access to people who need it for their work, keep it accurate, and avoid retaining obsolete contact details without a business reason. The EU General Data Protection Regulation includes principles concerning purpose limitation, data minimisation, accuracy and storage limitation. [2] Apply them with advice suited to your organisation’s obligations.
A structured B2B retailer onboarding process is the best place to gather these details before the first order. It gives the retailer clear fields to complete and gives your team a defined review point before the account becomes active.
Who should own and approve changes to retailer master data?
Customer data ownership means assigning named responsibility for the quality and approval of retailer account information. It does not mean one person must perform every update.
A workable model separates requesters, editors and approvers:
| Change type | Typical requester | Typical approver |
|---|---|---|
| Buyer, accounts payable or receiving contact | Retailer contact or account manager | Account owner or operations lead |
| Delivery instructions or new delivery location | Retailer contact or account manager | Operations lead |
| Legal name, registration number or VAT ID | Authorised retailer representative | Finance or designated data owner |
| Price list, discount or currency | Sales lead or pricing owner | Commercial owner |
| Payment terms or credit-related details | Sales or finance | Finance owner |
This division matters because not all fields carry the same risk. A typo in a contact’s job title is not the same as a change to the invoiced legal entity or customer-specific pricing. Make approval proportionate to the impact of the field.
The account manager often knows the customer best, but finance should have a defined role in approving data that affects invoicing, credit or tax handling. Operations should own fulfilment-critical delivery rules. A data owner can resolve disputes when different teams hold conflicting information.
Keep a simple change log: what changed, who requested it, who approved it, when it took effect and which previous value was replaced. This is especially helpful when an order, invoice or shipment needs to be investigated later.
Three colleagues reviewing a retailer account card before it joins an orderly workflow
How often should B2B customer records be reviewed and updated?
B2B customer records should be reviewed on an event-driven basis and through a regular account review routine. A record does not stay correct merely because it was correct at onboarding.
Review the relevant fields when an account:
- changes legal entity, ownership or registered details;
- asks for a new billing or delivery location;
- changes its purchasing or accounts payable contacts;
- moves to a new market, territory, currency or price list;
- requests revised payment or commercial terms;
- has been inactive and is returning to order.
Also include master-data checks in normal account management. Before a new season, assortment launch or commercial renewal, ask whether delivery locations, contacts, price lists and account permissions remain current. Before a high-value or unusual order, check the fields that matter to that transaction rather than assuming historic data still applies.
A short review checklist works better than a broad request to “confirm all details.” Tell the retailer exactly what they need to confirm and give internal teams a clear place to record the result.
How can a wholesale platform keep retailer data consistent with accounting?
A wholesale platform can keep retailer data more consistent by making an approved account record available across retailer onboarding, ordering, fulfilment and invoicing. It reduces the need to re-key the same company name, address, contact and commercial rule in separate places.
For example, a branded B2B storefront can collect retailer onboarding data at the source, route the account for internal approval, and allow approved users to order against their assigned catalogue, currency and delivery locations. Order management then carries the selected account data forward into the invoice workflow.
That connection is useful only when ownership rules remain clear. A platform should enforce the workflow you choose; it should not silently treat every submitted change as correct. Legal entity changes, VAT details, payment terms and pricing exceptions still need human review.
Brandgate is one example of a connected wholesale workflow: it combines a branded distributor portal with retailer onboarding, multi-currency catalogues, VAT-aware invoicing, order management and Fortnox integration. [3] When configured around a clear customer master record, this can reduce duplicate handling between sales and finance while preserving approval points.
For teams using Fortnox, define which system is responsible for each data field before enabling synchronisation. Decide, for instance, whether finance owns the accounting customer ID and payment terms, while the wholesale platform owns retailer user access and permitted delivery locations. Then test new accounts, updates, duplicate prevention and exception handling before making the process routine. Our guide to Fortnox accounting sync covers the planning questions in more detail.
A retailer storefront, order box and accounting ledger connected in one continuous workflow
Put the record at the centre of wholesale operations
Start with a small, reliable model: one account ID, one approved legal entity record, separate addresses and delivery locations, role-based contacts, commercial rules and a visible approval status. Next, document who owns each important field and what triggers a review.
Once that foundation is in place, onboarding, ordering and invoicing become easier to connect without losing control of the data. If you are assessing a branded wholesale portal and connected order-to-invoice workflow, Book a demo with Brandgate to discuss how your account structure and Fortnox process could work in practice.