Connecting your vendor's Webmercs shop

Who can do thisWorkspace Administrator

The Webmercs connection is how Flexshop orders from your vendor. When a Flexshop request is fully approved, Flexshop sends it to your vendor's Webmercs shop as an order, through this vendor connection. You set it up once, in the Hub. How requests are approved and what happens to them in Flexshop is covered in the Flexshop articles.

This connection places real orders

The form opens with a warning box, This connection places real orders. Webmercs has no test mode. Once the connection is enabled, every fully approved request becomes a real order at the vendor. Agree a test arrangement with your vendor before you enable it, for example a test customer account, or orders they cancel.

What you need from your vendor

• The shop's API address: the vendor's Webmercs shop address followed by /api/business/v1. Each vendor has its own address.
• An API username and password, issued by the vendor.
• The email of an existing, active Webmercs user in your account, usually your Webmercs administrator. Juvaro never creates Webmercs users.

Create the vendor connection

1. Open Marketplace, find the Webmercs card (category Purchasing) and click Add. The sheet New vendor connection opens.
2. Under Connection, fill in:
   • Connection name: starts as "Webmercs". Change it if you like.
   • Shop API address: for example https://shop.vendor.example/api/business/v1. It must start with https:// and must not contain a username, password, query string or fragment.
   • API username and API password.
   • Order user (your Webmercs administrator's email): required. Every order is placed under this Webmercs user, and the order confirmation goes to this address. The employee who ordered gets a copy at their sign-in email.
3. Optionally choose a catalogue under Catalogue. See Webmercs catalogue campaign and products bought before.
4. Under Check and enable, click Test connection (see below).
5. Switch Enabled on when the test passes and your vendor is ready. It is off on a new connection.
6. Click Save.

The form may also show a line such as "Juvaro connects to your vendor from <address>." If your vendor limits API access by address, ask them to allow that address for your account only, together with your own API user and password: other Juvaro customers can connect from the same address.

The password goes into Juvaro's secret vault and is never shown again. When you edit, leave API password blank to keep the saved one. If you change the shop address, you must enter the password again: "Enter the API password again: the shop now has a different address, and a saved password is only ever sent to the address it was entered for."

Test the connection

Webmercs is the only connector in the Hub with a Test connection button. The test reads one order from the shop with the details you entered and checks that the order user is an active Webmercs user. It never places an order.

• A pass reads "Connected: Connected to the Webmercs business API." If you chose a catalogue campaign, a second line confirms it, for example "Catalogue campaign: Your Company 2026, 312 products."
• A failure reads "Not connected:" followed by the reason, for example a wrong password or an order user that is not active.
• The test is limited to 10 per minute per workspace: "Too many connection tests from this workspace in the last minute. Wait a minute and try again."

Enabling it

• Saving with Enabled on runs the test first. The connection is only saved enabled when the test passes; otherwise you get "Not saved: an enabled connection must pass the connection test first. The test answered: …".
• Only one vendor connection can be enabled at a time, because Flexshop sends orders to exactly one. A second one is refused with "This workspace already has an enabled vendor connection. Disable or delete it first: Flexshop sends orders to exactly one vendor connection."
• While none is enabled, approved requests are not sent anywhere: Flexshop marks them as not sent, and an administrator can order them by hand.

After saving

On Connections the vendor connection is listed under "Outbound (out of Juvaro)" with the trigger On approval. It never runs on a schedule. Its page has Edit and Delete in the header and two cards. The Vendor connection card shows Shop, API user, Password (Set or Not set) and Order user, the note "Flexshop sends each fully approved request to this shop as an order. Nothing runs on a schedule, so there is no run history here." and a Test connection button. The second card shows the stored credential.

• The vendor connection is not charged: it uses no credits.
• Members never see it. It is hidden from them on Connections, Credentials and in the counts, because it holds the shop address and the API user.
• A Flexshop Application Administrator who is not a Workspace Administrator cannot see or change it either: "Only a workspace administrator can view or change the vendor connection."

Deleting it

Delete asks for confirmation in the dialog Delete vendor connection: "Flexshop stops sending approved requests to this shop, and the stored password is removed. Orders already placed at the vendor are not affected." See Deleting a connection.