A test order did not arrive by FTP or API

You placed a test order, but the supplier's FTP server or API didn't receive anything.

This article is about test orders. If a real order line shows Failed, A send to a supplier failed applies instead.

Why

FTP Upload and API Call don't place test orders at the supplier, and Dropday creates no order file for a test order. Suppliers you send orders to by email do receive them, marked "TEST EMAIL:".

What you can check before going live

The connection. In the FTP Upload settings, test the connection: Dropday writes a test file and shows the IP addresses your supplier may need to allow. For an API Call, test the call from its settings. This checks the connection or that single call, not an order.

The content of the order file. For a CSV order file, use the preview in the order file editor. For other order files, ask Dropday for an example. To receive a real file yourself, add a separate test supplier with the same file template and your own FTP server, and place a real order for it; the file then arrives on your server, not at the real supplier.

For an API Call, the request body is a template you write. Dropday fills it with the order data, and the call fails if the result isn't valid JSON.

The supplier's processing. FTP Upload and API Call only send real orders, so whether your supplier processes your orders correctly shows with the first real order, not with a test.