a. Drafts vs. Orders

An ‘Order’ isn’t an order until it’s fully paid. Any order that is not fully paid is a ‘Draft’. Because of this, Wholesale orders should be handled outside of VS. Learn how to manage Orders/Drafts here

b. Transactions vs. Order/payment date

V2 reports on Order dates and Payment dates. V3 reports on Transactions. Why? This makes for dead accurate reporting, creating a snapshot in time for whichever date range you are reporting on.

c. Concept of ‘Unpaid’ orders has gone away in V3

There is no concept of ‘Unpaid’ orders in V3. Any unpaid ‘orders’ are Drafts. Learn more about how Orders are handled here



Incredibly powerful reporting tool incorporating graphs, charts and downloadable reports. Because reports are based at the transaction level, reporting in V3 is very accurate.

Learn all about the Dashboards here


a. Master Sync happens in background as a ‘drip’

You no longer need to manually click a synchronize button - entire list is synchronized in real time.

b. Sync individual Groups (as opposed to entire list like in V2)

Flexibility to sync based on Group - makes for a faster sync. Learn about the MailChimp sync here

c. MC Automations: ROI reporting and Abandoned cart emails.

Create beautiful automated abandoned cart emails. Learn more here.

Get robust ROI reporting on your email campaigns. Learn how here


a. Products and SKUs

A Product is the umbrella (say, 2018 Syrah), and the SKUs are the individual items for sale (750ml, 1.5L, 375ml). This replaces the Parent/Child SKU relationship in V2.

b. Product Tags used for front-end filtering. We now have Product Tags (say, Syrah, Chardonnay, Merchandise). These act as Filters on the front end (either VineSpring Hosted Storefront or custom site using the SDK). Learn how Products/SKUs work here

c. Inventory: In V2, you can create as many inventory pools as you’d like for whatever reason. This can create a lot of confusion especially where human-error is concerned. We also found that most clients were referring to their fulfillment house(s) for master inventory numbers - therefore the VS pools were simply not being utilized effectively. We now have just one streamlined inventory pool. V3 inventory is simply a tool to prevent overselling of your DTC products. It is not meant to be a full-blown inventory management program. Note that sometimes it’s possible to hook up (via API) to various fulfillment houses so that inventory can be pulled directly from there. Learn about Inventory here


a. Custom Clubs

Allow your club members to customize their club shipments via the Account interface. Learn about Custom Clubs here

c. Automation and automatic filtering when processing a Club Release.

Club preview notifications automatically are sent to members including CC updates.

Learn about How Clubs work here


a. Choose front end default customer view

You have a choice of the default view being condensed or expanded to include images, etc.

b. Ability to choose start date for each Tier Level

Tier levels work independently in V3 (as opposed to all or nothing)

c. Ability to have multiple Allocations open at once (only one allocation can be open at one time in V2).

Learn more about Allocations here

7. CONNECTIONS - all new in V3!

a. Ability to connect many 3rd party applications with just a few clicks (ex: ShipStation, Calendly). Learn more here

b. Ability to send/receive data via API and Webhooks to other systems (ex: Salesforce) Learn more here

Please read

There are a few items that are not yet in the system but will be in the future. If these features are important to your business, you should consider waiting until these features are released into the V3 prior to migrating.

Multiple shipments - There can only be one shipment per order at this time. (For instance, if you have a customer who wants to take 2 bottles now but wants to ship 4 bottles home, this will need to be on two separate orders. Note that this can be accomplished using the Square integration, but not yet with the VS POS or Admin.

Split payments - There cannot be split payments on an order at this time. (In other words, if you have a tasting room, and two friends want to split a case of wine, you’ll need to create two separate orders for them. Note that this can be accomplished using the Square integration, but not yet with the VS POS or Admin.

For customers that are migrating from Auth.net to VineSpring Payments and are using Clubs, we recommend being on VS Payments for 2 months (or two billing cycles) prior to cutting over to v3.

Did this answer your question?