This guide explains how to connect your Evri business (Hermes) account to StoreFeeder. Use it if your Evri documentation lists SIT and PROD credentials.
Before you start
You'll need these details from Evri. Start with your SIT (test) credentials:
| Field | What it is |
|---|---|
| API Username | Your API username. |
| API Password | Your API password. |
| Account Client ID | Your Evri client ID. |
| Account Client Name | Your Evri client name. |
All four are required. StoreFeeder can't generate or look these up for you: ask Evri if you haven't been given them. You'll replace the SIT credentials with your PROD (live) credentials later, in Step 5.
Step 1: Start a new integration
- Click Settings at the top right of the page. The Integration Manager opens.
- Click + New Integration, then select Courier as the integration type.
Step 2: Choose Hermes
Select Hermes from the list of couriers.
Step 3: Name the integration
Enter a name for the integration, then click + Add Integration.
Step 4: Enter your SIT credentials
The Integration Details page opens.
- Choose your Company Identity, and change the Profile Name if you want to.
- In the Courier API Settings section, enter your SIT API Username, API Password, Account Client ID and Account Client Name.
- Click Save at the bottom of the page.
Step 5: Switch to your live credentials
- Contact StoreFeeder support so we can enable your account to use the test credentials. You can then generate a test label to send to Evri.
- When Evri has approved it, contact StoreFeeder support again so we can enable PROD credentials.
- Replace the SIT credentials with your PROD (live) credentials on the Integration Details page, and click Save.
Next, add shipping methods for the Evri services you use. See Creating a Shipping Method.
Troubleshooting
My Evri documentation doesn't mention SIT or PROD credentials
Use the standard Evri integration. See How to integrate with Evri.
I can't print a test label
StoreFeeder support needs to enable your account for test credentials first (Step 5).
Comments
0 comments
Article is closed for comments.