Skip to main content

Connect VeraCore

This is the first step for every other page in this section. It takes about two minutes, assuming your 3PL has already given you credentials.

Before you start

Ask your 3PL for four things. They are all issued by VeraCore, and none of them can be guessed:

You needLooks likeNotes
UsernameA web service userNot your VeraCore web login — ask specifically for API/web service credentials
Password
System IDA short identifierIdentifies your account within their VeraCore installation
Server Namerhu001, rhu126The subdomain of their VeraCore server, not a full URL

Server Name is the one people get wrong. It is the short server code (rhu001), not https://rhu001.veracore.com and not their company name. If your 3PL sends you a URL, the piece you need is the bit before the first dot.

If you don't have a VeraCore account yet

VeraCore is your 3PL's system, not something you sign up for independently. Create one at veracore.com, or get in touch with us and we will help you work out what to ask your warehouse for.

Create the connection

  1. Go to Apps & Integrations, open the Shipping & Fulfillment category, and choose VeraCore. The VeraCore Setup page opens.

  2. Give the connection an Instance Name. It defaults to VeraCore, and anything descriptive works — it is the label you will see in lists and in the job tray. If you connect more than one 3PL account, name them after the warehouse or the client so you can tell them apart at a glance.

  3. Fill in Username, Password, System ID, and Server Name from your 3PL.

  4. Choose the SKU.io warehouse this connection mirrors, under Choose a Warehouse to map to VeraCore. The list shows your direct and 3PL warehouses.

    Picking a direct warehouse converts it

    If you select a warehouse whose type is direct, a red note appears telling you it will be converted to a 3PL warehouse. That is a real change to the warehouse, not just a label — stock in a 3PL warehouse is mirrored from the provider rather than managed by you.

    If that is not what you want, create a new 3PL warehouse first and select that instead.

  5. Click Test Connection. This needs only the four credential fields — the warehouse is not involved — so you can test as soon as you have typed them.

    • Connection successful! — the credentials reach VeraCore and authenticate.
    • Connection failed — see what a failure means below.
  6. Click Create Integration. This button stays disabled until all four credentials and the warehouse are set. You land on the connection's Dashboard, with a VeraCore integration created successfully! confirmation.

What is on, and what is not

A new connection is deliberately quiet. Nothing is sent to your 3PL and nothing ships until you turn it on.

In particular, Enable Fulfillment starts off. Sales orders are not submitted to the warehouse until you enable it on the Settings → Fulfillment tab, which means you can set up mappings and check the catalogue without risking a real pick.

When Test Connection fails

A failure at this stage is almost always one of four things, in rough order of likelihood:

SymptomUsually means
Fails immediatelyServer Name is wrong — a full URL was pasted, or the code is mistyped
Fails with an auth errorUsername/password are your 3PL's web login, not a web service user
Fails intermittentlySystem ID does not match the credentials — the pair has to belong together
Fails for everythingYour 3PL has not enabled API access on the account yet

The fastest path is usually a message to your 3PL asking them to confirm all four values together, as a set. Individually correct values from two different systems will not authenticate.

More diagnosis in Troubleshooting.

Next steps

In this order:

  1. Map VeraCore facilities to warehouses — discover your 3PL's buildings and point each at a SKU.io warehouse. Nothing lands anywhere until this is done.
  2. Sync the offer catalogue — pull the item list your 3PL holds.
  3. Map an offer to a product — work through whatever the automatic matcher could not resolve.

Only after those three is it worth enabling fulfillment or reading inventory numbers seriously. For the full picture of what moves in which direction, see How the VeraCore sync works.

Last verified: