Record-triggered Order automation and duplicate B2B orders
Key Takeaway
B2B checkout already creates the Order and the Order Summary, so a custom flow on Order that also creates an Order Summary causes duplicates. Exclude B2B web stores from that flow.
In a B2B Commerce store, checkout itself turns the buyer's cart into an Order and an Order Summary, often in the background after the buyer clicks "Place Order". Custom automation on the Order object can collide with that built-in process. The best-known case is a record-triggered flow that also creates an Order Summary, which leads to duplicate Orders and duplicate Order Summaries.
What checkout already does
B2B stores created with the LWR template in Spring '23 or later process orders asynchronously. The cart-to-order work runs in the background after the buyer places the order, which improves store performance and responsiveness.
Streamlined Place Order is on by default in B2B LWR stores created in Summer '25 and later. Because Streamlined Place Order creates the Order Summary, Order Summary creation is already part of the built-in checkout.