Integration Core · checked 2026-10-15
A connection is one link between iVendNext and one other system — one web store, one accounting system. It appears on the Connections list when its connector's setup page is saved.
The Connections list
Open it from the Hub's Your connections card. Each row shows the connection and one word for its state, the first that applies (see What the word on a connection means); the time in front of the word says how long.
- Connect a system starts a new connection (Set it up).
- The ⋯ menu has Email me a daily summary and Stop my daily summary, for an Integration Manager.
The connection
The first part of the form names the connection.
| Field | What it is |
|---|---|
| Connection Name | identifies this one connection; two shops on the same platform each get their own |
| Shown As | the name with its platform, shown wherever this connection appears |
| Registered Application | the application the connection runs as |
| Company · Country | set when the connection registers, from its own settings |
| Integration Type | the kind of system — ERP, Online store, Marketplace and others; it decides how many connections are allowed |
| Platform | the product being connected |
| Connected Account ID | the account that answered the test on the setup page; it stays the same if the address changes |
| Connection Pattern | how the connection works; only queued, two-way syncing is supported |
Open setup opens the connector's own setup page, where its address and sign-in details live. Integration Core never holds them.
Switch and certification
| Field | What it is |
|---|---|
| One Connection Per · Connections Allowed | from the Integration Type: how many connections of this kind may run — per site, per company, or per company and country. An ERP allows one per company; a web store allows any number |
| Last Registered On | when the connector last registered this connection |
| Certification Result · Certification Checked On | see below |
| Fields It Adds to Documents | fields this connection adds to records here, for other connections to read |
| Switched On | ticked by Switch on, cleared by Switch off |
| Switched On Or Off By · Switched On Or Off At | who last changed the switch, and when |
Certification Result
The result of the connector's certification run, made on a stand-in, never on this connection's own syncing:
- CERTIFIED — no check failed.
- REFUSED — a check failed, or the connector's description of itself was refused.
- INCOMPLETE — nothing failed, but some checks could not finish.
- Not Run — never run.
It is advice, not a gate: a connection may be switched on whatever it reads. Anything but CERTIFIED: ask whoever supports the connector before relying on it. Call support if it reads REFUSED on a connection already in use.
Switching it on and off
Press Switch off or Switch on at the top right of the form, and confirm.
- Off stops sending and applying. Changes that arrive while it is off are kept and wait; nothing is lost. A switched-off connection does not ring about the records waiting for it, but its money records still ring.
- On picks up the kept changes, oldest first: one batch at once, then about 500 an hour. The question lists anything the connector says is Still needed; you can switch it on anyway.
- Your name and the time are recorded either way.
- Only someone who may edit the connection — an Integration Manager or a System Manager — sees the button.
Switching off is the supported way to stop an integration. To replace an ERP connection, switch the old one off, then set up and switch on the new one; remove anything the old one created on the other system by hand.
Health
What the connection last reported about itself. Every field here is set by the system.
| Field | What it is |
|---|---|
| Sign-in Status · Sign-in Refused Since | whether the other system accepts the sign-in details, and since when it has refused them |
| Live Updates · Live Update Failures | whether the other system pushes changes here, and how many times that failed (below) |
| Connected System Reachable · Cannot Reach It Since | whether the other system answers, and since when it has not |
| Health Check Last Ran | when the connector's health check last ran — not proof the connection is working |
| Last Looked For Changes | when the connection last looked for changes; blank if it never reported |
| Last Run Stopped Part-Way | ticked when its last run stopped before finishing |
| Not Checked For Over a Day | ticked by an hourly check when it is switched on and last looked over a day ago |
| Has a Problem | ticked when it is switched on and anything the Hub counts is wrong with it |
| Connected System Version | the other system's version it was certified against |
Live Update Failures
How many times the other system's live updates have failed. On some connectors it rises only after updates have already stopped, so never read it as an early warning. Read the connection's word on the Connections list instead.
Retry policy
How hard the connection tries, and when it alerts. An Integration Manager can change these.
| Field | What it is |
|---|---|
| Maximum Tries | how many times one change is tried before it is left for a person; 24 unless changed |
| Alert After This Many Tries | an early warning before the limit; 6 unless changed |
| Lock Timeout (minutes) | see below |
| Check Every (minutes) | see below |
| Alert If Waiting Over (minutes) | see below |
Lock Timeout (minutes)
How long one send may hold its lock before an interrupted send is moved to Unverified — 30 minutes unless changed. The check runs every 5 minutes, so an interrupted send can take about 35 minutes to show as Unverified. It must be longer than a send can take.
Check Every (minutes)
How often the other system is checked for changes — 5 minutes unless changed. These are measured from it: when a connection counts as late, when an Unverified alert rings, and the Cannot reach alert (twice this, never under 150 minutes). These are not: an unconfirmed reversal or an accepted record rings after 4 hours, and a Set aside one after 12.
Alert If Waiting Over (minutes)
How long a record may wait before the bell rings — 1440 minutes (24 hours) unless changed. Waiting is not failing, but not forever.
Handled Record Types
The record types this connection handles, as its connector declared them at setup: each one's Record Type, Direction (in, out or both), Triggered By, Source of Truth (Ours: this system's copy wins; Theirs: the other one's), Carries Money and Record Format Version. These are set by the connector, not typed in.
Switched On on a row affects only Link manually for that record type (Record Links); every setup run turns it back on.
Technical details
For support: Interface Version, Setup Change Check, Admission Change Check and Retry Handler. All are set by the system and read from the installed connector. If the connector's setup changes outside Integration Core, the connection can switch itself off (see Switched itself off).
What the word on a connection means
The Connections list shows the first of these that applies. The connection's own form says it in a full sentence.
Live
Green: switched on, reporting, and nothing below applies. At go-live, trust a record crossing more than this word.
Sign-in refused
Red, Sign-in refused by … (with it is also unreachable when both apply; on the connection's own page, Sign-in refused · unreachable): the other system refused the sign-in details at its last check. Records are Set aside, not failed, and nothing is lost. A System Manager renews the details on the connector's setup page (Open setup); anyone else who may edit the connection sees Ask a System Manager, which assigns the connection to one. Work resumes by itself on the first accepted call. Call support if the renewed details are refused again.
Cannot reach
Red, Cannot reach …: the other system did not answer. Work is paused rather than retried against it; nothing is lost. Check that the other system is up, and whether its address changed — a System Manager changes it on the setup page. A short outage can still ring the bell on some connectors: check Cannot Reach It Since before escalating. Call support if the other system is up and answering and the connection still reads Cannot reach.
Switched off
Grey: the connection is off. Changes that arrive are kept and wait. The form says who last changed the switch and when. See Switching it on and off.
Switched itself off
The connection reads Switched off, last changed by Administrator, often right after an upgrade: the system switched it off because what the connector declares about itself changed.
- Do not simply switch it back on. Read the alert: it names what changed.
- Ask a System Manager to read the Error Log.
- If you are told to run the setup again, run it against the same system. Never point an existing connection at a different store or company — for a different system, create a new connection.
Call support, always, with the alert's text.
Not reported yet
Switched on and never reported back. Blue: still inside its Check Every (minutes) plus an hour, so nothing is wrong yet. Grey: that window has passed and it is overdue. Never read either as running. Grey: ask whoever runs your site to check that the site's scheduled jobs, and the connector's, are running. Nothing alerts you about this one — you have to look.
Not checked
Red: the connection was reporting, and has stopped looking for changes within its own schedule plus an hour. Anything that only arrives when it looks is not being picked up. Ask whoever runs your site whether the connector's scheduled job has stopped.
Stopped part-way
Red: the connector recorded that its last run stopped before finishing — for example the other system moved, a firewall blocked it, or an answer could not be read. Integration Core is told that it stopped, never why. Check the other system first; a System Manager may find the reason in the Error Log, if the connector wrote one. Only a connector that reports this can show it.