Troubleshooting and frequently asked questions (FAQ)

Troubleshooting and frequently asked questions (FAQ)


Here you will find common errors, known limitations and frequently asked questions about Order Drop API.



TABLE OF CONTENTS


Common errors


Error messageMeansSolution
Invalid JSON data passed in order field...The data is not valid or is missing required fields. At least one of the customer's email or customer number must be included and have a value – organisation number, customer ID or Tripletex ID is not enough aloneCheck the data structure, if necessary together with whoever built the integration
Duplicate order on sourceAn order with the same source reference already exists. Normal when the duplicate check is enabled – the order has already been importedIf the order is to be imported again anyway, the existing one must be deleted or the source reference changed
Missing customer in TelarisThe customer does not exist and «Reject missing customer» is enabledCreate the customer manually, or disable the setting to let the API create the customer automatically
Missing product in Telaris: [product reference]The product does not exist and «Reject missing product» is enabled. The whole order is deleted – no partial import. The error message includes the product referenceCreate the product with the correct product number/SKU, or disable the setting
No error message (403)The access key is missing, wrong, or the API user is disabled/deleted. Keys do not expire – a key that has worked does not stop working on its ownCheck that the key is sent correctly in the request



Known limitations


  • No user interface for the API – Order Drop API has no page of its own in Telaris. Orders are sent programmatically, and the result is seen in the order view

  • Product lookup follows a fixed order – the system always tries product number, then SKU, then OID. If several fields are given on the same line, the last match is the one that stands

  • No partial import – if «Reject missing product» is enabled and one product is missing, the whole order is deleted. An order is not created with the lines that did find products

  • The customer is not rolled back – if «Reject missing product» deletes the order, a customer that was created automatically in the same call remains in Telaris

  • No automatic update – an order created via the API cannot be updated by sending the same order again. Changes are made manually in the order view

  • Address format – the delivery address is stored as free text unless «Update delivery address» is enabled. Free text is less structured and can cause challenges when printing labels

  • Order creation only – the API creates orders, but cannot update, cancel or delete existing orders



What the module does not do


  • Order status update – the API does not update the status of existing orders in Telaris or in the external system
  • Product sync – does not synchronise products between Telaris and the external system
  • Stock status – does not send stock levels back to the external system
  • Invoicing – orders imported via the API are handled as ordinary orders and are invoiced via Telaris' ordinary invoicing process
  • Returns – the API does not handle returns or credit notes



Frequently asked questions


What is Order Drop API?

A receiving point in Telaris that lets external systems send orders into Telaris automatically. Integrations such as WooCommerce and Telaris Connect use this in the background.

Do I need a licence to use Order Drop API?

No. Order Drop API is part of the base system. You only need an API user with an access key.

What happens to the customer when an order is received?

The system attempts to find the customer based on customer number, email or other identifiers. If it does not exist, it is created automatically – unless «Reject missing customer» is enabled.

What happens if a product does not exist in Telaris?

The order line is added without a product link – only text and price from the data sent in. If «Reject missing product» is enabled, the whole order is rejected instead.

Can the same order be imported twice?

By default yes – the API does not automatically check for duplicates. But the sending system can enable the duplicate check by sending a source reference and a duplicate-check flag.

What is the difference between using Order Drop API directly and via an integration?

No functional difference – integrations such as WooCommerce and MyStore use Order Drop API under the hood. The difference is that the integrations handle data retrieval and formatting automatically, while direct use requires the external party to build this themselves.

Do orders created via the API become visible in the order list?

Yes. They are ordinary orders in Telaris and appear in the order list, on the customer card and in all reports.

Can I see which orders have been imported via the API?

Customers created via the API are marked with a tag (for example «orderdrop»). In addition, a source reference is stored on the order that can be used to search and filter.

Who can send orders to the API?

Anyone with a valid API key. There is no restriction on who can send – access is governed solely via the key.

Are the order lines released automatically?

Yes, by default all order lines are released immediately. The sending system can disable this per order, so the lines remain unreleased and must be handled manually.

Can I receive an email when a new order comes in?

Yes. Configure an email address in the system settings for orderdrop notification. The message contains the order number and a direct link to the order.



Glossary


TermExplanation
Order DropThe process of sending order data to Telaris via the API
API keyAccess key that authenticates calls to the API – created for an API user in Telaris
API userA separate user type in Telaris intended for system integration – has an access key instead of a password
Access keyUnique key that authenticates calls to the API
Source referenceExternal reference number from the sending system – used for duplicate check and traceability
Duplicate checkCheck that rejects orders if one with the same source reference already exists
Product linkingThe process where an order line is linked to an existing product based on product number, SKU or OID
ReleaseOrder lines are marked as ready for picking and warehouse handling
TagLabel placed on customers created via the API for traceability in the customer search
Address objectThe 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
Product OIDUnique identifier for a product in Telaris – different from product number and SKU
API documentationTechnical documentation for developers describing data format and authentication for the API







Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article