Workflows

Check OTTO order status: Which orders are ready for processing?

Find OTTO order items ready for processing with AI. Distinguish ANNOUNCED, PROCESSABLE and SENT, check mixed orders and include older open items.

To prepare orders for shipping on OTTO, look for order items with fulfillmentStatus: PROCESSABLE. ANNOUNCED does not yet authorise shipping; SENT identifies items already recorded as shipped. Check each item within an order. A single order can contain products at different stages of processing.

With Backlane, you can check these status records in an AI chat and create a worklist. The Backlane documentation explains the connection; the practical guide to analysing marketplace data with AI covers the general process. The following prompts are templates that have not been run against a seller account. They read data and create checklists. Shipping the goods remains a separate task.

What do ANNOUNCED, PROCESSABLE and SENT mean?

What matters is the status of each physical unit, which OTTO calls a “Position Item”. This also allows several units of the same SKU to be tracked separately. The OTTO order documentation describes the status values and transitions.

Item statusMeaningNext check
ANNOUNCEDAnnounced, but not yet released for shipping preparation.Check stock reservation and the subsequent status change.
PROCESSABLEReleased for processing.Add the item to the shipping worklist and check warehouse progress.
SENTRecorded as shipped through the shipments interface.If there is a query, check the associated shipment.
RETURNEDRecorded as returned.Continue checking through the returns process.
CANCELLED_BY_PARTNER / CANCELLED_BY_MARKETPLACECancelled by the seller or marketplace respectively.Exclude from the shipping worklist.

ANNOUNCED alone is not an error. OTTO describes an initial waiting period during which customers can still cancel; prepayment orders may remain in this state longer. OTTO recommends reserving stock for these items. This does not yet authorise shipping. See the OTTO recommendations for announced orders.

Likewise, SENT does not prove delivery to the customer. Shipment data belongs to a separate object, described in the OTTO shipments interface documentation.

Why can a simple status filter miss items?

OTTO distinguishes between the order’s lifecycle and a match on at least one item. In the default BUCKET mode, the other items also influence which status filter returns the order. With mode=AT_LEAST_ONE, one matching item is enough for the order to appear. The Orders interface search modes explain this distinction.

For a complete worklist of items ready for processing, use fulfillmentStatus=PROCESSABLE together with mode=AT_LEAST_ONE. Then retain only the items within those orders that actually match. An order appearing in the results does not mean every item it contains may be shipped.

How do you include older open orders?

Start with the open backlog, not “orders placed today”. An older order can still contain work even if it falls outside a selected order-date range. Filtering for recently modified orders can also exclude open cases that have not changed.

For this check, initially omit fromOrderDate, toOrderDate and fromDate. The date parameters and cursor pagination are documented under Orders V4 in the OTTO API Index. Showing a small sample is fine as long as the analysis reads every result page and identifies the sample as such.

Create a read-only shipping worklist for my OTTO connection
[connection name]. Do not change orders or shipments.

Search with fulfillmentStatus=PROCESSABLE and mode=AT_LEAST_ONE.
Do not set order-date or modification-date boundaries.
Follow every nextcursor page. Then retain only PROCESSABLE items
and count each salesOrderId/positionItemId combination once.

Show the total number of these items and the 20 oldest by
processableDate: order number, item identifier, SKU, status,
processableDate and expectedDeliveryDate where available.
List missing processableDate values separately; do not replace
them with the order date. State the number of items not displayed.

State the source, connection, retrieval time and completeness.
If pagination stops early, label the result as incomplete.
Do not display customer names, addresses or contact details.
Do not infer a shipping deadline from expectedDeliveryDate.

A successful query that reads all pages and finds no matching items means there are no matching open items for that connection. Missing permissions or an interrupted request are different outcomes and must not be presented as “no open orders”.

Which item should you check first?

Use processableDate, where available, to inspect the items that have been ready for processing longest. This field records entry into PROCESSABLE. By contrast, orderDate is the date the order was placed. They answer different questions: “When was it ordered?” and “When did it become ready for processing?” The fields are defined in the Orders V4 response schema in the OTTO API Index.

expectedDeliveryDate refers to the expected delivery date. A date that is approaching or has already passed is a reason to investigate, but it does not provide a binding shipping deadline. That assessment may also require transit times, shipping agreements or current warehouse information. Missing date values should remain visible in the checklist.

A useful priority might be: “Ready for processing for three days; check warehouse progress.” A claim such as “must ship by 14:00 today” requires an independently evidenced deadline. The AI chat should keep those statements separate.

What does this look like for a mixed-status order?

Fictional example: Order EXAMPLE-A contains three lamps. Item 1 is SENT, item 2 has been PROCESSABLE for two days, and item 3 is cancelled. Only item 2 belongs on your shipping worklist. Neither shipping all three lamps again nor excluding the entire order would be correct.

A second example order contains one ANNOUNCED item and one PROCESSABLE item. This is where AT_LEAST_ONE helps: the item ready for processing should be found despite the mixed order. The announced item remains excluded. These are two independent checks within the same order.

How do you recheck an order before processing it?

Read the selected order again before turning the worklist into an action. Statuses can change between the overview and processing. You can retrieve an individual order by its order number and compare its items.

In my OTTO connection [connection name], check only the order
with order number [order number], using read-only operations.

Compare its current items with this earlier checklist:
[item identifier, earlier status and earlier retrieval time].

For each item, show SKU, earlier and current fulfillmentStatus,
plus processableDate, sentDate and expectedDeliveryDate where available.
Separate items still PROCESSABLE from those now SENT,
cancelled or in other states. Do not invent reasons for changes.

State the new retrieval time and missing values. Do not display
customer names, addresses or contact details. Do not mark
anything as shipped, cancel anything or send messages.

This creates a verifiable shipping worklist: clearly identified items, their current status and a justified next check. Your warehouse process must confirm whether the goods have already been packed. Order status alone cannot establish that.

Ask your own data the next question.

Connect your seller accounts with Backlane and use the available data in your AI assistant.

Set up Backlane