Cin7 Omni and Shopify B2B: What to Consider Before Building a Trade Portal

For many wholesalers, distributors and growing product businesses, Cin7 Omni plays a central role in inventory, order management, fulfilment and operational control.

It helps manage products, stock, sales channels, orders, suppliers, warehouses and integrations. For businesses with multiple channels, complex inventory needs, EDI requirements or advanced operational workflows, Cin7 Omni can become one of the most important systems in the business.

But when the business starts thinking about B2B eCommerce, one question usually appears:

Should we use Cin7 Omni’s own B2B capability, or build a Shopify B2B trade portal connected to Cin7 Omni?

There is no universal answer.

Cin7 Omni and Shopify B2B can both play important roles. The right architecture depends on your customers, pricing model, catalogue complexity, fulfilment process and long-term digital roadmap.

This article explains what wholesalers and distributors should consider before building a Shopify B2B portal with Cin7 Omni.

Why Cin7 Omni and Shopify B2B are often considered together

Cin7 Omni is designed for product businesses that need stronger inventory and order management across multiple channels. Cin7 positions Omni as a solution for more complex needs, including native EDI and 3PL integrations, advanced multi-entity support, extensive eCommerce integrations, automation and reporting.

Shopify, meanwhile, has continued to expand its B2B capability. Shopify’s B2B features can include companies, catalogues, payment terms, contact permissions, self-serve ordering and Shopify Flow automations, with specific availability depending on the plan.

This creates an attractive model.

Cin7 Omni can continue to manage inventory, order operations and fulfilment, while Shopify B2B provides a modern customer-facing trade portal.

For many businesses, that is the ideal separation:

Cin7 Omni manages the operational backbone.

Shopify B2B manages the customer experience.

The integration layer is what makes that model work.

Why build a Shopify B2B portal if you already use Cin7 Omni?

Some Cin7 customers may ask why Shopify B2B is needed at all.

Cin7 offers B2B online store capability and describes its B2B portal as a way to support online B2B sales and accounting integration.

For some businesses, a Cin7-native portal may be enough. This may be especially true where the business needs a simple trade ordering experience with limited custom UX, limited marketing requirements and relatively standard account workflows.

However, Shopify B2B may be more attractive where the business wants:

• A more polished customer-facing experience.
• Stronger brand control.
• Better merchandising.
• More flexible content management.
• A more modern front-end experience.
• Stronger SEO and landing page capability.
• B2B and B2C commerce in one platform.
• Shopify’s app ecosystem.
• More control over campaign pages and customer journeys.
• A long-term commerce platform that can scale beyond a basic trade portal.

The choice is not simply “Cin7 portal vs Shopify portal”.

The real question is:

What type of B2B buying experience do your customers expect, and how much control does your business need over that experience?

What should Cin7 Omni own?

Before building a Shopify B2B portal, the business needs to define the source of truth.

In most Cin7 Omni and Shopify B2B environments, Cin7 should usually own the operational data.

That may include:

• Products and SKUs.
• Stock on hand.
• Available stock.
• Warehouse locations.
• Customer records.
• Wholesale pricing.
• Order management.
• Fulfilment workflows.
• Purchase orders.
• Supplier data.
• EDI workflows.
• 3PL connections.
• Invoices or financial documents, depending on the architecture.
• Inventory reporting.

Cin7’s API documentation notes that its REST API includes endpoints for products, pricing, stock information, orders, payments and contacts.

That means Cin7 Omni can often provide many of the core data points required for a connected B2B portal.

The important step is to decide what data should be synchronised to Shopify, what should be queried from Cin7, and what should be handled by middleware.

What should Shopify B2B own?

Shopify B2B should usually own the customer-facing commerce experience.

That may include:

• Website design and UX.
• Navigation.
• Product browsing.
• Search.
• Product content.
• Category landing pages.
• Customer login.
• Company profiles.
• B2B catalogues.
• Checkout.
• Promotions.
• Content pages.
• Campaign landing pages.
• Analytics and marketing tags.
• Customer self-service experience.

Shopify’s B2B model includes companies and company locations, with settings for payment terms, shipping addresses, contact permissions, catalogues, tax exemptions and checkout settings.

For a trade portal, this is important because the customer experience often needs to feel much better than a simple ordering form.

B2B buyers still want speed, clarity and confidence. They want to log in, see the right products, view the right pricing, check availability and place orders without calling customer service.

The main integration flows to consider

A Cin7 Omni and Shopify B2B portal will typically involve several integration flows.

Some may be handled by existing connectors. Others may require customisation, middleware or API work.

Cin7’s Shopify integration documentation describes Shopify as an integration option for synchronising order management and inventory across sales channels, shipping integrations, accounting platforms and more. Cin7 also provides Shopify setup and product upload documentation for Omni.

However, a B2B portal often requires more than a standard product and order sync.

The key areas to review are below.

1. Product data

The first decision is how product data should move between Cin7 Omni and Shopify.

This may include:

• SKU.
• Product name.
• Product status.
• Barcode.
• Brand.
• Category.
• Product type.
• Variant structure.
• Units of measure.
• Dimensions.
• Weight.
• Images.
• Descriptions.
• Technical attributes.
• Related products.
• Substitute products.

Cin7 may be the source of truth for core product and SKU data. Shopify may be the better place to manage customer-facing descriptions, merchandising, images, landing page content and SEO.

For many businesses, this creates a split model.

Cin7 owns the operational product record.

Shopify owns the customer-facing product experience.

If the product catalogue is large or technical, a PIM may also be required.

2. Stock availability

Stock visibility is one of the most important parts of a B2B trade portal.

Customers may need to know:

• Whether a product is available.
• How much stock is available.
• Which warehouse has stock.
• Whether an item can be backordered.
• Expected lead time.
• Whether incoming stock is available.
• Whether stock is allocated to another channel.
• Whether stock should be hidden from certain customers.

Cin7 promotes real-time inventory visibility and multi-channel stock control as key inventory management benefits.

For Shopify B2B, the integration should define how that stock data appears online.

For example:

• Should customers see exact stock counts?
• Should they only see “in stock” or “available to order”?
• Should availability differ by customer location?
• Should Shopify use stock buffers?
• Should backorders be allowed?
• Should stock be reserved after checkout?
• Should Shopify show stock by warehouse or consolidated stock?

Getting this wrong can create overselling, disappointed customers and manual order correction.

3. Customer accounts and companies

Shopify B2B is structured around companies and company locations.

This matters for wholesalers and distributors because one customer account may have multiple buyers, branches, locations or permissions.

Before building the portal, define how Cin7 customer records should map to Shopify companies.

Key questions include:

• Does one Cin7 customer equal one Shopify company?
• Do Cin7 delivery addresses map to Shopify company locations?
• How are users invited or approved?
• Who can order on behalf of the company?
• Who can view order history?
• Can customers manage their own users?
• Can customers request account access from the website?
• How are inactive or blocked customers handled?
• What happens when customer details change in Cin7?

Shopify B2B supports company account requests, companies, company locations and account-specific settings.

The integration design needs to ensure that these structures align with how the business already manages customers in Cin7.

4. Customer-specific pricing and catalogues

Pricing is often the hardest part of a B2B portal.

A Cin7 Omni customer may have:

• Standard wholesale pricing.
• Customer-specific pricing.
• Price tiers.
• Contract pricing.
• Promotional pricing.
• Customer group pricing.
• Channel-specific pricing.
• Regional pricing.
• Product exclusions.
• Different catalogues by customer type.

Shopify B2B supports catalogues that can be assigned to companies and company locations. These catalogues can control product availability and pricing for B2B customers.

The key decision is whether Shopify can store the customer pricing model, or whether pricing needs to be calculated or synchronised from Cin7.

In simpler models, prices may be synchronised into Shopify B2B catalogues.

In more complex models, middleware may be required to transform Cin7 pricing into Shopify structures.

In highly complex models, real-time pricing may need to be considered, though that can add performance and architecture complexity.

Before development starts, the business should map:

• How many price lists exist.
• How customer-specific the pricing is.
• How often prices change.
• Whether pricing is tax-inclusive or tax-exclusive.
• Whether discounts are calculated dynamically.
• Whether different units of measure affect price.
• Whether promotional pricing exists.
• Whether Shopify’s catalogue model can support the requirement.

This is one area where assumptions can become expensive.

5. Payment terms and checkout rules

B2B customers often buy on account rather than paying immediately by card.

Shopify B2B supports payment terms, which define how long a company has to pay for an order. Payment terms can be set for company locations.

Before launching a Shopify B2B portal, define how payment terms should work.

Consider:

• Which customers can buy on account?
• Which customers must pay upfront?
• Are payment terms stored in Cin7, accounting software or Shopify?
• Are deposits required?
• Are purchase order numbers mandatory?
• Should credit limits be checked before checkout?
• Should some customers be blocked from ordering?
• Should payment method options differ by customer?
• How are tax rules applied?

For simple trade accounts, Shopify’s B2B payment terms may be enough.

For more complex credit management, external validation from Cin7, accounting software or middleware may be required.

6. Order submission

Order flow is the core of the integration.

When a customer places an order in Shopify B2B, the business needs that order to reach Cin7 accurately and reliably.

The integration should define:

• How Shopify orders are created in Cin7.
• How customer accounts are matched.
• How company locations are mapped.
• How purchase order numbers are passed.
• How line items are validated.
• How tax and freight are handled.
• How discounts are represented.
• How payments or terms are recorded.
• How order notes are passed.
• How backorders are handled.
• How duplicate orders are prevented.
• How failed orders are retried.

This needs to be tested with real B2B scenarios, not only simple retail-style checkout.

Examples include:

• A customer ordering on account.
• A customer ordering products from a restricted catalogue.
• A customer using a purchase order number.
• A customer ordering more than available stock.
• A customer with multiple delivery locations.
• A customer reordering from order history.
• A customer using negotiated pricing.
• A customer placing an order that requires manual review.

The portal is only successful if customers can order confidently and the operations team can fulfil without manual rework.

7. Fulfilment, shipping and tracking

Once an order is placed, customers expect visibility.

For B2B, fulfilment can be more complex than B2C.

An order may be:

• Partially fulfilled.
• Split across warehouses.
• Backordered.
• Picked by a 3PL.
• Delivered by company fleet.
• Sent via freight carrier.
• Held for account review.
• Delayed due to supplier availability.

The integration should define how fulfilment status flows back to Shopify.

This may involve Cin7, a 3PL, freight system, warehouse system or middleware.

Customers may need to see:

• Order received.
• Order processing.
• Partially shipped.
• Backordered.
• Shipped.
• Delivered.
• Cancelled.
• Credited.
• Tracking details.

For a trade portal, this is a major customer service opportunity.

If customers can self-serve order and fulfilment status, the business can reduce calls and emails while improving the buying experience.

8. Invoices, credits and account history

Many B2B portals become more valuable when customers can access more than ordering.

Customers may also want:

• Order history.
• Invoice downloads.
• Credit notes.
• Statements.
• Returns.
• Account balances.
• Backorder status.

The business needs to decide whether Shopify should show this data natively, pull it from Cin7, pull it from accounting software, or display it through a custom account portal.

This is often not part of a simple Shopify implementation, but it can be valuable for wholesalers and distributors.

The more self-service value the portal provides, the more likely customers are to adopt it.

9. Cin7’s native Shopify connector vs custom integration

A key decision is whether the native Cin7 Shopify integration is enough.

For some businesses, it may be.

Cin7 Omni’s Shopify documentation covers installation, settings and product upload workflows, which can support a standard connection between Cin7 and Shopify.

However, a Shopify B2B trade portal may require additional review.

The native connector may not cover every business rule, particularly where there are complex B2B requirements such as:

• Company and company location mapping.
• Customer-specific Shopify B2B catalogues.
• Complex price list transformation.
• Account terms and credit validation.
• Restricted catalogues.
• Multi-warehouse availability logic.
• Backorder rules.
• Invoice and credit note visibility.
• Custom fulfilment status.
• Exception dashboards.
• Custom middleware workflows.

The right answer may be:

• Native connector only.
• Native connector plus configuration.
• Native connector plus custom middleware.
• Fully custom API integration.
• Hybrid architecture.

The decision should be made after discovery, not assumed at the start.

10. Exception logging and monitoring

Integration failures are inevitable.

The question is whether the business can see them, understand them and resolve them quickly.

For a Cin7 Omni and Shopify B2B integration, common failures may include:

• Product sync errors.
• Stock sync delays.
• Price mapping errors.
• Shopify company mapping failures.
• Orders failing to create in Cin7.
• Duplicate order attempts.
• Invalid SKUs.
• Missing customer records.
• Tax or freight mismatches.
• Fulfilment updates failing.
• Payment term mismatches.
• API authentication issues.
• Rate limit or timeout issues.

A strong integration should include exception logging and monitoring.

That may involve:

• Structured logs.
• Retry queues.
• Failed order dashboards.
• Alerts for critical failures.
• Daily exception reports.
• Business-friendly error messages.
• Monitoring through tools such as New Relic.
• Traceability from Shopify order to Cin7 order.

This is especially important for B2B because customers may place larger, more operationally important orders than a standard retail customer.

A failed order sync is not just a technical problem. It can become a customer service, warehouse and revenue problem.

Shopify B2B portal discovery checklist

Before building a Shopify B2B portal with Cin7 Omni, the business should answer the following questions.

Customer accounts

• How are customers structured in Cin7?
• Do customers have multiple buyers?
• Do customers have multiple locations?
• Do different users need different permissions?
• Who can invite or approve users?
• Are any customers blocked or inactive?

Products and catalogues

• Which products should appear online?
• Are catalogues customer-specific?
• Are any products restricted?
• Are product descriptions managed in Cin7, Shopify or a PIM?
• Are images and SEO content managed in Shopify?

Pricing

• How many price lists exist?
• Is pricing customer-specific?
• Are discounts dynamic or fixed?
• Are prices tax-inclusive or tax-exclusive?
• How often do prices change?
• Can Shopify B2B catalogues support the pricing model?

Stock

• Should customers see exact stock?
• Should stock be shown by warehouse?
• Are backorders allowed?
• Are stock buffers needed?
• How often should stock sync?
• What happens if stock changes during checkout?

Orders

• How should Shopify orders map into Cin7?
• Are purchase order numbers required?
• Are payment terms supported?
• Are credit limits checked?
• How are failed orders handled?
• How are duplicate orders prevented?

Fulfilment

• Where does fulfilment status come from?
• Are orders split across warehouses?
• Are tracking numbers available?
• Can customers see partial fulfilment?
• Can customers see backorder status?

Support and monitoring

• Who owns integration support?
• How are errors logged?
• Who receives alerts?
• What is the retry process?
• What does customer service see?
• How quickly must order failures be resolved?

This checklist should be completed before design and development begin.

Common mistakes to avoid

The most common mistake is treating Shopify B2B as a simple website build.

For Cin7 Omni customers, the trade portal is usually an operational system. It needs to connect properly to inventory, pricing, customers, orders and fulfilment workflows.

Other common mistakes include:

• Assuming the native connector covers every B2B requirement.
• Not mapping Cin7 customers to Shopify companies properly.
• Underestimating customer-specific pricing.
• Duplicating pricing logic in too many places.
• Showing inaccurate stock online.
• Ignoring backorder rules.
• Not testing payment terms.
• Forgetting purchase order numbers.
• Not designing for failed order syncs.
• Failing to involve customer service and warehouse teams.
• Building a portal that looks good but does not match operational reality.
• Launching without exception monitoring.

A strong Shopify B2B portal needs both a good customer experience and a good integration architecture.

One without the other is not enough.

When Shopify B2B is a good fit for Cin7 Omni customers

Shopify B2B can be a strong fit when the business wants:

• A modern trade portal.
• Better customer self-service.
• B2B and B2C commerce in one platform.
• Stronger merchandising and content control.
• Improved SEO and marketing capability.
• Faster ordering for trade customers.
• Account-specific catalogues and pricing.
• A better customer experience than a basic portal.
• Integration with Cin7 Omni for products, stock, pricing and orders.

It is especially attractive for wholesalers and distributors that want to modernise the front-end buying experience while keeping Cin7 Omni as the operational system behind the scenes.

When a simpler Cin7 B2B portal may be enough

A native Cin7 B2B portal may be enough when the business:

• Needs a simple trade ordering experience.
• Has limited UX or brand requirements.
• Does not need advanced content or SEO control.
• Does not need B2C and B2B in one platform.
• Has relatively simple customer account structures.
• Wants to avoid a larger Shopify implementation.
• Is primarily solving internal order entry efficiency.

This can be a practical option for some businesses.

However, if the goal is a more strategic digital commerce channel, Shopify B2B may provide more room to grow.

Final thoughts

Cin7 Omni and Shopify B2B works well together when each system has a clear role.

Cin7 Omni should remain the operational backbone for inventory, order management, fulfilment and business data.

Shopify B2B should provide the customer-facing trade portal experience.

The integration between them is what determines whether the portal succeeds.

Before building, wholesalers and distributors should carefully map products, stock, customer accounts, pricing, payment terms, orders, fulfilment and exception handling.

A successful trade portal is not just a nicer way to place orders.

It is a connected digital channel that reflects the real operating rules of the business and makes buying easier for customers.

When Cin7 Omni and Shopify B2B are integrated properly, the result can be a modern trade experience that customers want to use and internal teams can trust.