Migrate from Legacy B2B to B2B online store
Overview
Legacy B2B uses technology that is no longer supported or compatible with the Cin7 Omni platform.
Cin7 Omni no longer provides, for Legacy B2B:
technical support
security updates
bug fixes
other forms of assistance and support for the product
We recommend migrating to the B2B online store.
Legacy B2B vs B2B online store
We recommend upgrading from Legacy B2B to the B2B online store.
Some of the new B2B online store features are:
A mobile friendly and improved customer experience.
B2B promotions (including discounts depending on order value or volume of products).
Multiple B2B online stores.
Customers can bulk order (excludes UOM).
Hiding or displaying product options, UOMs, BOM kits.
Secure customer login (customers can reset their own passwords).
3PL integration (sends orders to 3PL).
Integration with the Cin7 Omni Payment Portal.
Most Legacy B2B functionality.
Legacy B2B features not available in the B2B online store
There are some Legacy B2B features that don't exist in the B2B online store. We will not provide every feature from Legacy B2B, but we are working on developing the features critical to our customers.
Display product without login
In Legacy B2B, customers can view products without logging into their account. This is not available in the B2B online store and it is not in our roadmap.Consignment orders
Unlike Legacy B2B, the B2B online store can't create sales orders for multiple branches. You can set the default branch for sales orders in the Order Settings. You can set the consignment branch as the default branch, and create multiple B2B stores for your different branches. Multiple branches may incur an additional fee depending on your Cin7 Omni plan.Minimum order value or quantity
Setting the minimum value or amount of products for an order is in our roadmap for the new B2B online store. Until then, we recommend that you add a message on your checkout to cover any requirements for customers before they order. You could also create UOM products, so all products meet the value or quantity threshold.
Migrate to the B2B online store
You can migrate from Legacy B2B to the B2B online store by:
Installing the B2B online store from the
App Store.
Installing B2B promotions from the
App Store.
-
Set up your B2B online store. You can also reuse your old legacy B2B domain.
You can optionally use your Legacy B2B domain for your new B2B online store.
Select
Integrations and then select your B2B online store.
Select
Settings and then select the Store Details tab.
Add a temporary custom domain. For example, your store name followed by b2b.cin7.com (storename.b2b.cin7.com).
Set up your B2B online store and test it works correctly. Invite yourself as a customer to explore the B2B online store.
Contact our support team to use your Legacy B2B domain on this new B2B online store.
Test your B2B online store and then invite your customers.
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB