The documented behavior

Kalshi V2 processes an order batch sequentially in request order. A 201 response has a result for each item, with an identifier for success or an error object for failure. Timeout or unavailable errors can leave placement uncertain. Some preliminary checks reject the entire batch before orders are sent. Kalshi · Batch Create Orders V2 ↗

How a duplicate position arises

Imagine three instructions: the first returns an order ID, the second has invalid parameters and the third has an uncertain outcome. Resending the whole batch risks repeating the first instruction. Instead, map each original intention to its result, correct the rejected one and reconcile the uncertain one. Save local identifiers before submission.

Showing the result to staff

Display the batch's overall progress with a separate state for each row and access to its raw response. Accepted, rejected and unreconciled counts explain the remaining work. Test mixed responses and connection loss after submission. This is especially important for linked positions whose exposure changes when only part of a batch executes.