{"section":"known-issues","requestedLocale":"en","requestedSlug":"order-again-flow-in-b2b-suite-can-lead-to-orders-placed-with-wrong-marketing-data","locale":"en","slug":"order-again-flow-in-b2b-suite-can-lead-to-orders-placed-with-wrong-marketing-data","path":"docs/en/known-issues/B2B/order-again-flow-in-b2b-suite-can-lead-to-orders-placed-with-wrong-marketing-data.md","branch":"main","content":"## Summary\n\nWhen re-ordering an order from an organization (A) through the Orders History Order Again flow, then changing to other organization (B) and re-ordering another order from this organization through the same flow, the second order can be created with organization A's `orgId` and `costId` on its `marketingData`\n\n## Simulation\n\n- Have an user registered on two organizations, A and B, on a store using B2B Suite\n- Place Order A using Organization A\n- Place Order B using Organization B\n- Log in as Organization A\n- Re-order Order A through the Order's History Order Again button, being redirected to checkout\n- Check that the IPS cookie UTM tags will be set as the `orgId` and `costId` from Organization A by the `/marketingData` request made by `b2b-checkout-settings`,\n- Change org to Organization B\n- Re-order Order B through the same flow, being redirected to checkout\n- Check that:\n  - The IPS cookie UTM tags will still have the same values: `orgId` and `costId` from Organization A\n  - No new `/marketingData` request will be made by `b2b-checkout-settings`\n  - The orderForm will have its marketingData set with `orgId` and `costId` from Organization A\n\n- If you proceed with the order, it will be placed with org B data, but with org A's tags.\n\n## Workaround\n\n** **\n\n1. Delete the IPS cookie before re-ordering in a different organization than the one you originally used\n2. Add query parameters to the `/createBy` re-order request with the `orgId` and `costId` of the current organization"}