Which Visma product do you use?
Visma is a product family, not a single system. The right integration depends on which Visma product your business runs:
Visma.net is a cloud ERP for mid-to-large Nordic businesses. It covers invoicing, inventory, purchasing and financial management in one system — and supports B2B price lists, multi-currency and OSS VAT reporting for EU sales. Visma.net is typically the master for article records, customer records and stock levels.
Visma Spiris (formerly Visma Spcs) is a cloud business system for Swedish SMEs. Spiris handles invoicing, basic inventory and accounting, and functions as the master for product catalogue and pricing toward the webshop.
Visma eEkonomi is a cloud accounting system for smaller businesses. Simpler than Spiris, but can be connected to ecommerce for orders and basic article sync. See the Visma eEkonomi ecommerce integration guide for specifics.
Visma Business and Visma Business NXT are available through Junipeer on request, as installations vary significantly in configuration.
All Visma products can be connected to Shopify, WooCommerce, Magento and other ecommerce platforms via Junipeer.
What syncs — and in which direction?
A Visma integration with your ecommerce platform handles four types of data:
Orders (ecommerce to Visma)
Orders placed and paid in your webshop are sent to Visma automatically for invoicing and fulfillment. In Visma.net a sales order is created with the correct customer, price list and VAT code. In Spiris and eEkonomi the order is registered for invoicing without manual entry.
Articles and prices (Visma to ecommerce)
Visma is the master for your product catalogue. New articles added in Visma sync to your webshop with name, description, price and SKU. Price changes in Visma update the webshop directly — you maintain prices in one place and both systems stay current. For Visma.net users with B2B customers, the integration fetches the correct contract prices per customer directly from the ERP.
Stock levels (Visma to ecommerce)
Visma is the master for inventory. When a goods receipt is registered in Visma, the stock level in your webshop updates without manual work. This prevents overselling — a common problem when the webshop shows outdated numbers until someone manually exports and updates them.
Returns and credit notes (ecommerce to Visma)
Returns processed in your webshop automatically create a credit note in Visma linked to the original order. Stock is adjusted if the item is returned to inventory. The bookkeeping stays accurate without manually creating credit notes in Visma.
Shopify + Visma
Shopify combined with a Visma business system is the most common combination among Swedish ecommerce merchants. The integration handles the full data flow:
- Shopify orders are sent to Visma as customer orders or invoices
- Visma article records and prices update the Shopify storefront
- Visma stock levels sync to Shopify and prevent overselling
- Returns in Shopify create credit notes in Visma linked to the original order
- B2B customers in Shopify fetch their contract prices directly from Visma.net
See the Shopify – Visma.net integration page or the Shopify – Visma Spiris integration page for setup details.
WooCommerce + Visma
WooCommerce stores running Visma.net or Visma Spiris use the same core flows. WooCommerce orders go to Visma for invoicing, and stock and articles are driven from Visma to WooCommerce. See the WooCommerce ERP integration guide for more detail.
Common problems without integration
Stock levels are wrong. The webshop shows a balance that does not reflect the real position in Visma. Customers order items that are out of stock — and the store has to handle cancellations and customer contact manually.
Manual order entry does not scale. Moving Shopify orders to Visma manually takes 5–15 minutes per order. At 30 orders per day, that is a half-time job. The integration removes that work entirely.
Price drift. Price changes in Visma do not appear in the webshop until someone logs in and updates manually. With Visma as the master, prices are always in sync.
OSS VAT and EU sales. Visma.net supports OSS reporting with the correct VAT code per EU country. Without correct configuration in the integration, you risk errors in VAT reporting at audit. See the VOEC and OSS VAT guide for configuration details.
How long does setup take?
A Visma.net or Visma Spiris integration via Junipeer typically takes 15–30 minutes to configure the core flows. What takes longer:
- Mapping to your chart of accounts and VAT codes
- OSS configuration per EU country, if relevant to your business
- Test sync with real order data to verify the flow
Visma Business and Visma Business NXT require a separate scoping conversation because installations vary in configuration and data structure.
For a broader comparison including Fortnox and Business Central, see the ERP ecommerce integration guide.