iVendNext WooCommerce connector · version 2.1.0.136 · checked 2026-10-29
The connector keeps a WooCommerce store in step with iVendNext. This page says what crosses in each direction and what does not. A company can connect several stores. Each store is its own connection.
What goes from iVendNext to the store
- Catalog, prices, tax and stock. Products, variations, categories and brands go to the store. Prices go as the regular price. Sale prices stay the store's.
- Stock. Stock goes out for the warehouses you choose, less a buffer you set for each warehouse. It goes on a sweep every five minutes by default, and only while the scheduled check is running. Every hour, iVendNext reads the store's own stock figures, prices and tax rates, and corrects them.
- Items you disable. An item you disable, or move out of the web catalog, is hidden on the store. When you put it back, it gets the status it had before. A product the merchant moved to the store trash stays in the trash.
- Pictures and descriptions. A product picture, description and short description are sent once, when the product is first created on the store. They are never sent again, so a web team that retakes photos or rewrites copy keeps its version. A variation, a category and a brand carry their own picture, sent once the same way. You can send a new main picture on purpose with Send picture to store on the item.
- Tax rates and classes. iVendNext sends tax rates, and sends each product its WooCommerce tax class once you map your tax templates to the store classes.
- Tracking and fulfillment. The order's fulfillment status and the tracking number go back to the store as a note the buyer can see. For an order the shopper collects, the note starts "Ready to collect from" and names the shop. It carries no tracking number.
- Invoices. An invoice reaches the store as a private order note. With the iVendNext plugin, a signed-in shopper sees each invoice and credit note of their own order on the order page and can download a PDF. A guest without an account sees none.
Put the pictures on your items before the first Load Catalogue. A picture added afterward does not reach a product that already exists. The store fetches a picture from your iVendNext site, so the connection Public URL must be filled in, and the file must be a normal attachment, not a private one. A picture given as a web address is sent whatever the Public URL says. If the store cannot fetch a picture, iVendNext sends the product again without it, so the product still arrives.
How stock works
- A till sale lowers the store figure at the next sweep, not at shift close. The figure is less what your tills sold and have not yet posted.
- A unit sold online comes off the store figure once the order reaches iVendNext, and stays off until the shop ships it.
- A product bundle (a gift set) shows the number of complete sets your chosen warehouses can make up, counted warehouse by warehouse. Two candles in one shop and the box in another make none. A set that is short of a component goes out of stock on the store. New products arrive as drafts, so a shopper sees a set only after you publish it.
- While an order waits to be booked in iVendNext (on hold, or waiting for a decision), WooCommerce has already counted it. iVendNext never writes a higher stock figure over the store's for those items until the order is booked.
- The buffer narrows the chance of selling the last unit twice. It never removes it. iVendNext stock is not real time, and the connector cannot promise that a unit will not be sold twice.
- The store shows one stock figure, the ticked warehouses added up. A shopper can choose a shop that has none. The store cannot reserve stock at checkout.
What comes from the store to iVendNext
- Customers. A customer arrives at sign-up, or at the first order if the connection is set to On First Order.
- Orders and payments. An order arrives once it is paid, or in a status you import. On a Sales Order connection, a paid order arrives with its payment kept as an advance. A Delivery Note ships it, and iVendNext makes an invoice for exactly what shipped, paid from the advance. Cash on delivery has no advance and is invoiced at delivery. On a Sales Invoice connection, each order books as an invoice when it arrives.
- Refunds. On a Sales Order connection, a refund before invoicing comes back out of the order advance, and the goods it names come off the order. A refund of the whole order closes the order if nothing has shipped. An order that is on hold, or one still owing a free item, is not closed by itself, and iVendNext says what is left to do. After invoicing, a refund becomes a credit note against the invoice, left open for Accounts to settle the payout.
- If parcels made two or more invoices, the refund is credited on the invoice that billed its goods. A refund for an amount alone goes to the oldest invoice with room. A shipping or fee refund goes to the one invoice that carries that charge. iVendNext asks a person only when no single invoice can take it.
- A refund with no advance to return it from, which is usual for cash on delivery, waits for the invoice that is made when the order ships. It is then credited by itself. The cash taken at the door is not booked by itself. Accounts book it by hand.
- A refund the store states as 0.00 credits no money and names the goods.
- A refund the store restocked puts the goods back into iVendNext stock, against the delivery that shipped them. A serial-tracked item, a batch-tracked item or a bundle is named for a person instead.
- On a Sales Invoice connection, a refund is a credit note against the invoice.
- Collect orders. For an order the shopper collects from one of your shops, the shop they chose is the warehouse the sale books and delivers from. You map each pickup location to its warehouse first. An order for a location you have not mapped waits and names it, and it comes in by itself once you map it. The store shows no pickup time slots.
Vouchers from the till
A voucher is one code, for one shopper, good for one use. A till prints it on a receipt.
- You choose which coupon campaigns a store accepts (Coupon Campaigns on the connection). Nothing crosses until you do.
- A voucher appears on the store as an ordinary WooCommerce coupon. The shopper types the serial number from the receipt into the store coupon box. When they spend it online on a paid order, iVendNext closes the voucher on its side. When they spend it at the till instead, it is taken off the store.
- Only a percentage voucher for one named product crosses. The store takes the percentage off at most the voucher's Applicable Quantity units. The mobile till takes it off every unit. On a basket with more units than that quantity, the store gives less than the mobile till. For example, 6 units at 50.00 and a quantity of 1 give 5.00 on the store and 30.00 on the mobile till.
- A campaign whose Applicable Quantity is 0 or a fraction is refused. So is a campaign whose product the till sells in a unit other than its stock unit. A fixed-amount voucher is refused. So is a voucher for a whole item group, a brand or the whole basket. Each refusal gives its reason on the connection.
- A voucher crosses only if the till issued it to a customer with an email address. The store accepts it only from that address, because a serial number is not a secret.
- Every hour, iVendNext reads each voucher back from the store. It puts back a change someone made to a live voucher. It reports a voucher the store switched off, and a use it cannot explain, such as an order still waiting for payment. Until you act on that report, the till can still accept the voucher.
- The two systems come into step every few minutes. A voucher spent at the till and online inside that window can be spent in both places. The exposure is the value of that one voucher, once in each place it can be spent. With two storefronts on one campaign, that is three places. Do not tell a customer that cross-channel coupons are safe.
- Campaign promotions do not cross as coupons. With the plugin option Till promotions, which is off until you tick it, the store cart is priced with the promotions your tills run, each as a Promotion line. A promotion the cart cannot carry faithfully is refused by name. If iVendNext cannot be reached, the cart stays at its normal price and the sale goes through. A promotion limited within one sale, or to special days of a customer, is refused.
Points and gift cards
iVendNext is the one place that keeps each balance. The plugin shows and requests. It keeps nothing.
- A signed-in shopper sees their points and can pay with points at the classic and the block checkout. They can also check a gift card balance on My Account.
- iVendNext takes the points off once. On a Sales Invoice connection that happens when the order arrives. On a Sales Order connection it happens at the first invoice, when the order ships. Until then the same points can be spent on a second web order.
- The discount never takes more than the points are worth. On a store whose prices exclude tax and whose basket mixes tax rates, it can take a few cents less.
- Points are earned online only when the loyalty program awards points on Sales Invoices, and its plan has start and end times set. The shipped default awards nothing online. We tested earning on our own test bench, not on a real store.
- You cannot spend a gift card online.
- Points spent on an order are not returned if the order is refunded. On a Sales Order connection, an order refunded in full before it is invoiced never takes them.
- The shop needs coupons switched on in WooCommerce, and iVendNext priced in the same currency as the store.
Tax
- Map an Item Tax Template to a store tax class, and iVendNext sends that rate into the class. A reduced or exempt rate crosses by itself.
- A template with several rate rows goes out one store rate per row. An order books each row tax to that row account. We tested this to the cent against native iVendNext invoices.
- The store says whether its prices include tax. iVendNext says the same on its tax templates. When the two disagree, iVendNext refuses the rate and gives the reason.
- Mapping one Item Tax Template to one store class makes that class rate at every tax jurisdiction you send. With 12 jurisdictions and two mapped classes, you get 36 rates on the store, and more when a template has several rows.
- A rate the store has in a class you have not mapped waits. An operator links it by hand: Record Links, then Link manually.
- Unmapping a template leaves its products in the class they last had. Change them on the store, or map the template again.
- On a store whose prices include tax, a shopper outside the shop base address whose rate differs pays a different total than at the till, unless the plugin option Same price everywhere is on and the plugin is connected. An order created through the store API is still priced from the shop address.
- The tax setup of every customer differs, and iVendNext creates no tax template of its own. Ask about the template, not the country.
Several stores
Each store is its own connection, with its own price list, warehouse and section of the catalog. We ran two test stores on one company, and one buyer ordering on both produced one iVendNext customer with a link for each store. We have not run two live merchant stores.
- A warehouse mapped on two connections is offered twice. Its stock counts in full toward both stores, so together they can promise more units than exist. Give each store its own warehouse, or keep a bigger buffer.
- On a Sales Order connection, the second store's order is refused when it has the same order number as another store's order. The message names two ways out: change Selling Settings, which lifts that check for every Sales Order on the site, or book that order by hand.
Setup needs two people
Setup needs a System Manager beside the Integration Manager, for the store keys, for Register and for granting read on the records you map. An Administrator is not needed. After the store address or keys change, nothing is sent to the store, and the scheduled check pauses, until someone presses Test Connection again. Orders that the store notifications deliver still import.
Not in this release
- A product tag, web address (slug) or SEO fields. They stay the store's.
- A description kept in step after the product exists.
- Gift card spending online.
- Reserving stock at checkout.
- A return request that a customer starts online. A refund that the store restocks is in.
- Coupons and promotions beyond those named above.
- Customer groups.
- Changing an order after it is placed.
- Pickup time slots, and stock for each shop on the store.
- Serial and batch numbers.
- Shipping rate calculation.