How to Set Up Customer-Specific Pricing in Magento for B2B Accounts

B2B buyers rarely expect every organisation to pay the same amount. A hospitality group ordering cartons of supplies, a trade customer buying electrical components, and a government department purchasing equipment may each require a different rate, payment arrangement, or minimum order value. Magento can support these requirements when pricing rules are designed around customer accounts rather than individual shopping sessions.

The platform offers several ways to manage business-to-business pricing, including shared catalogues, customer groups, tier prices, negotiated quotes, and catalogue price rules. The best approach depends on whether you need a small set of standard discounts or a fully personalised price list for every company account.

For Australian retailers moving away from older retail systems, pricing should be planned alongside inventory, tax, account management, and order fulfilment. The NCR Retail Online website reflects the wider shift towards connected ecommerce operations, where online orders and business records need to remain consistent across sales channels.

Choose The Right Magento Pricing Model

Magento customer groups are suitable when several accounts share the same commercial terms. You might create groups such as Wholesale, Trade, Dealer, Education, and Government, then apply different prices or discounts to each group. This is simple to administer and works well when a business has broad pricing bands.

Shared Catalogues are more appropriate when companies need a controlled product range and account-specific rates. Adobe Commerce B2B allows an administrator to create a custom catalogue for a company account, assign products, and set prices for that account or its associated customer group. Buyers see the agreed products and rates after signing in.

Tier pricing is useful where the discount depends on quantity rather than the identity of the customer. For example, a café in Melbourne might receive one rate for 10 cases of a product and a lower rate for 50 cases. A negotiated company price can then sit alongside the tier structure if a particular account has a separate contract.

Configure B2B Company Accounts

Begin by enabling the relevant B2B features in the Magento administration panel. Depending on your edition and configuration, this may include company accounts, shared catalogues, negotiable quotes, purchase orders, and payment on account. Confirm that the installation supports the features you intend to use before building a pricing structure around them.

Create each organisation as a company account rather than treating every employee as an unrelated shopper. Add the legal business name, Australian Business Number where appropriate, sales representative, billing details, shipping addresses, and account status. Company administrators can then manage their own buyers, roles, and approval permissions.

A company may have separate purchasing staff in Sydney, warehouse users in Brisbane, and finance staff in Perth. Magento company roles can limit what each person can do, such as placing orders, viewing quotes, or approving purchases. This reduces the risk of an employee accessing commercial information that belongs to another department.

Create Shared Catalogues And Price Lists

In the catalogue management area, create a shared catalogue for a defined customer segment or individual account. Select the products that should be visible, remove retail-only items, and assign the applicable price for each product. Use a clear naming convention that makes the catalogue easy to audit, such as “National Hardware Trade” or “Queensland Hospitality Group”.

Set prices in a way that matches your commercial agreements. A fixed company price is appropriate when contracts specify exact amounts. A percentage discount may be easier when wholesale rates change with the standard retail price, although it needs careful governance so that a future retail price update does not produce an unintended wholesale rate.

Take care with products that have configurable options, bundles, or custom attributes. Check whether the customer-specific amount applies to the parent product, its simple components, or both. Test the displayed price, cart total, tax calculation, and order export for each product type before assigning the catalogue to a live customer.

Apply Rules For Special Commercial Terms

Catalogue price rules can handle broad promotions or conditional discounts, such as 8% off selected cleaning products for an approved trade group. Conditions may be based on customer group, product attribute, category, quantity, or date range. They are useful for campaigns and structured discounts, but they should not replace a formal contracted price list when exact rates matter.

Cart price rules work after products are added to the basket. They can support free freight above a threshold, account-specific coupon codes, or a discount on a qualifying order. For B2B buyers, automatic application is usually safer than requiring staff to remember a code, particularly when customers place repeat orders through saved carts or purchase orders.

Set rule priorities and expiry dates deliberately. A promotional rule can accidentally override a negotiated price if the conditions overlap. Keep a record of which rule takes precedence, who approved it, and when it should expire. This is especially important during end-of-financial-year promotions and seasonal buying periods in Australia.

Connect Pricing With Tax And Business Systems

Australian B2B pricing must be reviewed alongside GST. Magento should display prices consistently as either tax-inclusive or tax-exclusive, according to the buying experience and configuration required for your business. Many trade customers expect ex-GST pricing, while public-facing retail shoppers generally expect the final GST-inclusive amount.

Confirm how GST applies to domestic sales, exports, freight, and exempt transactions. An account marked as wholesale does not automatically make every order tax-free. Your tax settings should reflect the customer’s location, product tax class, shipping destination, and any valid documentation required by your finance process.

Pricing also needs to flow correctly into inventory and accounting systems. If Magento connects with an ERP, POS platform, or warehouse application, make sure the integration passes the customer account, shared catalogue, discount, GST amount, and final line price. The compliance considerations in this regulatory transition guide are relevant when replacing legacy retail software and reviewing connected business processes.

Manage Security And Account Visibility

Customer-specific pricing is commercially sensitive. A buyer who can see another company’s rates may use that information during negotiations or share it outside the organisation. Restrict catalogue access to authenticated accounts, disable unnecessary guest purchasing for controlled products, and ensure that customer data is separated correctly in the website and API layers.

Use strong administrative access controls and multi-factor authentication where available. Keep administrator roles narrow, review inactive users, and record changes to pricing and company permissions. Magento patches should be applied through a controlled release process, with backups and testing before production deployment.

Australian businesses may also need to consider privacy obligations, payment security, retention of customer records, and the handling of personal information. When an account includes multiple staff members, document who is authorised to approve orders and whether a company administrator can invite or remove users.

For customers in regional areas, test the complete buying experience under realistic conditions. A buyer in Darwin or a mining operation outside Kalgoorlie may experience different connectivity and delivery constraints from a metropolitan customer. Even the principles used for beam coverage planning illustrate why service assumptions should be checked against actual locations rather than treated as universal.

Test Orders Before Launch

Create test accounts for each pricing scenario: standard retail, wholesale group, individual negotiated catalogue, expired account, and unauthorised visitor. Sign in as each user and verify the product visibility, unit price, quantity breaks, discounts, GST, freight, payment terms, and final order total.

Test the same account on desktop and mobile devices, then repeat the process through any connected sales channel. If your business has a mobile ordering application, review its account and pricing behaviour as carefully as the website; guidance on iOS app development highlights the importance of checking platform-specific functionality rather than assuming every interface behaves identically.

Ask sales, finance, warehouse, and customer service staff to approve the test results. Sales can check negotiated rates, finance can validate GST and account terms, and warehouse staff can confirm that product and quantity data reach fulfilment correctly. Use a staging environment for these checks and avoid testing price changes directly on a live store.

Maintain Pricing Over Time

Assign an owner to every shared catalogue and negotiated price list. That person should review contract dates, supplier cost changes, discontinued products, customer status, and margin performance. A price that was profitable six months ago may become unsuitable after freight, exchange-rate, or wholesale cost changes.

Build a repeatable import process if you manage hundreds of accounts. A controlled CSV import or integration can update SKU-level prices efficiently, but every file should be validated before publishing. Include account identifiers, SKU, currency, price, start date, end date, and approval status to make corrections easier.

Magento customer-specific pricing works best when commercial rules are documented outside the software as well as configured inside it. Define who may approve a discount, how exceptions are recorded, and what happens when an account changes ownership or payment status. For retailers selling homewares, hospitality products, or dining and entertaining ranges, consistent product data and category ownership are just as important as the price itself.

A reliable setup combines company accounts, shared catalogues, carefully prioritised rules, accurate GST settings, and thorough testing. Start with a small group of representative customers, compare Magento’s totals with approved contracts and accounting records, then expand the model once every department agrees that the results are correct. The practical rule is simple: every buyer should see the right products, the right contracted price, and the right tax treatment after signing in.