What is Order Drop API?
Order Drop API is Telaris' receiving channel for orders from external systems. The API takes in an order as structured data and creates it in Telaris – with order lines, customer data and delivery address. If the customer does not already exist, it is created automatically.
The API is the foundation for all order import in Telaris. Ready-made integrations such as WooCommerce, MyStore and Telaris Connect use Order Drop API in the background to bring orders in. In addition, external parties – customers with their own systems, partners or third-party developers – can connect directly to the API.
NOTE: Order Drop API is part of the base system and requires no licence. All that is needed is an API user with an access key.
TABLE OF CONTENTS
- What challenges does the module solve?
- Functional overview
- Typical workflow
- Interaction with other modules
- Key concepts
What challenges does the module solve?
Businesses that sell via a web shop, marketplace or other channels need to get orders into their order system without manual work. Typical problems:
- Manual order registration – without an integration, someone has to copy orders from the external system to Telaris by hand
- Errors and delays – manual transfer leads to typos, missing lines and delayed delivery
- Duplicate customers – customers from the external system must also be created manually in Telaris
- Lack of traceability – hard to know which orders have been imported and which remain
- Scaling – as volume grows, manual handling becomes unsustainable
Order Drop API solves this by:
- letting external systems send orders directly to Telaris via a simple API call
- creating the customer automatically if it does not already exist
- linking order lines to the right products based on product number or SKU
- releasing order lines automatically so the order is ready for further processing immediately
- sending an email notification to the responsible person on a new order (optional)
- rejecting duplicates based on source reference (optional)
Functional overview
| Function | Description |
|---|---|
| Order creation | Receives order data and creates an order with lines in Telaris |
| Customer handling | Finds an existing customer or creates a new one based on the customer data sent in |
| Product linking | Links order lines to products via product number, SKU or product OID |
| Delivery address | Stores the delivery address on the order – either as free text in the order note or as a structured address object |
| Duplicate check | Rejects orders with the same source reference as an existing order (optional) |
| Automatic release | Releases order lines automatically so the order is ready for picking |
| Email notification | Sends a message to an email address when a new order is created (optional) |
Typical workflow
- An external system (web shop, integration, partner system) sends order data to Order Drop API
- The API authenticates the request via the access key
- The customer is identified in Telaris – or created automatically if it does not exist
- The order is created with status «open»
- Order lines are added and linked to products in Telaris
- The lines are released automatically (unless disabled in the request)
- An email notification is sent to the configured recipient if applicable
- The API returns order number, customer number and status
Interaction with other modules
- The WooCommerce integration – imports orders from WooCommerce web shops via Order Drop API
- Telaris Connect – receives orders from connected Telaris instances via Order Drop API
- The order module – orders created via the API are handled as ordinary orders in Telaris
- The product module – order lines are linked to existing products based on product number or SKU
- The customer module – customers are created or reused automatically
For information: The same order intake is also used internally by the Tripletex integration when importing invoice data, and by order booking from the tag module. These go through the same logic as external order imports.
Key concepts
| Term | Explanation |
|---|---|
| Order Drop | The process of sending order data to Telaris via the API |
| API key | Access key that authenticates calls to the API – created for an API user in Telaris |
| API user | A separate user type in Telaris intended for system integration, not human login |
| Source reference | External reference number from the sending system – used for duplicate check and traceability |
| Product linking | The order line is linked to an existing product based on product number, SKU or product OID |
| Release | Order lines are marked as ready for picking and warehouse handling |
| Address object | The delivery address stored as a separate, structured record on the order (name, street, postcode, city, country), as opposed to plain text in the order note |

Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article