External partners

Technology vendor

The Technology vendor role is for manufacturers and integrators of warehouse automation equipment, such as robots, AGVs and PLC-controlled systems, who connect their technology to Ysend. In the dedicated Device test lab you test the devices assigned to your organisation against the platform, collect the evidence of each run in a compatibility report, and publish your models, prices, spare parts, contacts and app listings to Ysend.

Apply for access All role guides

Start-up guide

Send an application using the matching form. If it is approved, use the invitation you receive to sign in.
If you forget your password, choose “Forgot password”, then “Send recovery instructions”.
The Sign in button opens the app in this page’s language.
After you sign in, the “Device test lab” opens on “Devices”. The left rail holds every section of your workspace: “Devices”, “Runs”, “Motion windows”, “Models”, “Price List”, “App listings”, “Contacts”, “Spare parts”, “Webhooks” and “Connect site equipment”.
In the “Device fleet” table, check the devices assigned to your organisation: status, battery, last contact and the motion column, which shows either “Motion window active” or “Read-only”.
Open “Motion windows” to see the time windows granted to you for physical movement tests and their status: “Scheduled”, “Open now” or “Expired”.
Open “Models” and check the “Declared models” list; declare any model of yours that is missing before you start testing.
Open “Contacts” and use “Add contact” to register the people or teams Ysend should reach for technical and commercial questions.
Use “Account & security” at the bottom of the rail for your account settings, and sign out there when you leave a shared computer.

End-to-end workflows

Apply for partner access and open the Device test lab

Starts when: Your company manufactures or integrates warehouse automation equipment and wants to connect it to Ysend.

On the public Ysend page “Connect your technology to Ysend”, complete the form “Apply for partner access”: company name and work email are required, the other details about your equipment are optional.
Select “Submit application”. A confirmation tells you that the application has been received and will be reviewed.
The Ysend platform team reviews your integration. Once your application is approved, you receive an invitation to activate your partner account.
Activate the account from the invitation and sign in. The “Device test lab” opens directly on “Devices”.
Check the “Device fleet”: the devices Ysend has assigned to your organisation appear there. If the table is empty, devices have not been assigned yet.
Open “Motion windows” to see whether a movement test window has already been granted.

Result: Your partner account is active and the Device test lab shows your assigned devices and motion windows.

Next: The Platform administrator assigns devices and grants motion windows; you then test your devices and maintain your catalogue.

Test a device and share the compatibility report

Starts when: A device has been assigned to you, or you have changed its firmware, connection or configuration and need fresh evidence.

In “Devices”, find the device in the “Device fleet” table and select “Open device”.
In the “Live device view”, check that the device responds. If the address is wrong, correct the IP address and port with “Tune connection”.
Under “Test suites”, select “Run read-only suite”. This suite only reads data, so it does not need a motion window.
The run appears in “Runs” with the status “Queued”, then “Running”. Open it to follow the “Steps” and the “Wire captures” of every request and response.
Wait for the final status: “Passed”, “Failed” or “Stopped”. If you need to interrupt a run, select “Stop run” on the run page; “All runs” takes you back to the list.
For PLC-controlled equipment, open the “PLC I/O tests” card on the device page and select “Run conformance test”; the result is listed with the device’s conformance runs.
Select “Compatibility report” on the device page. The report lists the device identity, declared models, test activity, latest run, wire exchanges and motion windows granted.
Select “Print / save as PDF” to keep the report or send it.

Result: The device has a recorded test history with step results and wire evidence, and a compatibility report saved as PDF.

Next: Send the compatibility report to your Ysend contact; the Platform administrator uses it to decide on the next tests or on a motion window.

Run a motion test during a motion window

Starts when: The Platform administrator has granted a motion window for your device, shown as “Scheduled” in “Motion windows”.

In “Motion windows”, check the start and end of the window. When the start time is reached, its status changes from “Scheduled” to “Open now”.
In “Devices”, the motion column of the device now shows “Motion window active”. Select “Open device”.
Return to the device. In «Command console», select Dispatch delivery to reveal «Pick-up point» and «Drop point», then choose two discovered map points; do not send an ad-hoc delivery just to configure the test.
Under “Test suites”, select “Run motion suite”. The button stays disabled while no motion window is active or while one of the two points is missing.
Follow the movement in the “Live device view” and the exchanged messages in the “Wire log”. To interrupt, open the run in “Runs” and select “Stop run”.
Check the final status of the run (“Passed”, “Failed” or “Stopped”) and its “Wire captures”.
When the window ends, its status becomes “Expired” and the device returns to “Read-only”; only read-only tests remain possible.

Result: The motion suite has run inside the authorised window and its results are part of the device’s test history and compatibility report.

Next: Ask the Platform administrator for a new motion window if further movement tests are needed.

All features

Implementation

Automation integration testsView assigned robot devices, their status and battery, and recent test runs.

What you can open

The areas below describe the access assigned to this role.

Vendor test lab

Everyday tasks

Declare or update a model

Open “Models” and fill in the model form: model code, display name, integration mode, availability (“In stock”, “Made to order”, “Backorder”, “Discontinued”) and lifecycle (“Active”, “Deprecated”, “End-of-life announced”).
Select “Declare model”; the model appears in “Declared models”, where “Edit” lets you change it later.
Open the model to add its “Documents”, “Firmware” releases and “Self-reported compliance claims”.
To change many models at once, use “Bulk import / export (CSV)”: “Export current models”, edit the file, check it with “Preview (dry-run)”, then select “Apply import”. The import is applied completely or not at all.

Publish a price line

Open “Price List” and go to “Publish a price line”.
Enter the item code, optionally the model, your price to Ysend, the currency, the minimum order quantity and the “Valid from” date; leave the end date empty for an open-ended price.
Add quantity discounts with “+ Volume tier”. A new line with a later “Valid from” date schedules the new price and closes the current one.

Publish an app listing

Open “App listings” and select “New listing”; the listing is created as a draft.
Select “Promote” and use “Set current version” to define the version clients will receive.
Choose «Publish». Publication requires platform approval of your organization and a successful deployment scan; correct any reported refusal before trying again.
To stop new installations, select “Withdraw”; existing installations keep running. A published listing cannot be deleted.

Maintain spare parts, contacts and webhooks

In “Spare parts”, maintain your “Spare parts & accessories”: part number, category, compatible model codes, price and availability.
In “Contacts”, keep the published contacts up to date and use “Add contact” for new ones.
In “Webhooks”, on “Webhooks & PLM sync”, register an HTTPS endpoint, choose the events and an optional signing secret, then select “Send test” to check the delivery.

Connect site equipment through the edge agent

Open “Connect site equipment” and read how it works: the agent opens an outbound encrypted tunnel, so no inbound port has to be opened on the site.
Under “2 · Download the agent”, select “Download” and verify the file with its published checksum.
Enrol the site with its name and the equipment addresses (one per line), then select “Enroll & mint token”.
Copy the pairing token with “Copy Token” or “Copy run command”, store it safely and confirm with “Done — I saved it”: the token is shown only once. If it is lost, select “Rotate token”.

Limits and help

This role works only inside the Device test lab. You cannot assign devices to your organisation, open or extend motion windows, or use warehouse, order, transport or billing functions of Ysend; any other page brings you back to “Devices”. Movement tests are only possible during an active motion window. For device assignment and motion windows, contact the Platform administrator; for any other question, write to contact@ysendgroup.com.

contact@ysendgroup.com

Help centre

Common questions

Why is “Run motion suite” disabled?

The motion suite requires an active motion window for the device and both a pick-up point and a drop point in the “Command console”. Check “Motion windows”: the window must be “Open now”.

Can I test without a motion window?

Yes. “Run read-only suite” only reads data from the device and is available at any time; only tests that move the device need a motion window.

Where do I find the evidence of a test?

Open the run in “Runs”: every step is listed under “Steps”, and each request and response is kept under “Wire captures”. The “Compatibility report” of the device summarises all of it and can be saved with “Print / save as PDF”.

I have lost the pairing token of a site. What should I do?

The token is shown only once and cannot be displayed again. In “Connect site equipment”, select “Rotate token” for the site and install the new token on the agent.

Does withdrawing an app listing remove it from clients?

No. “Withdraw” stops new installations, but clients who already installed the app keep using it.