@mercurjs/docs 2.3.0 → 2.3.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -51,12 +51,17 @@ Order groups are created automatically during checkout by the `completeCartWithS
|
|
|
51
51
|
5. **Link everything** — The workflow creates links between:
|
|
52
52
|
- Each order and the order group
|
|
53
53
|
- Each order and its seller
|
|
54
|
-
- Each order and the cart's payment collection
|
|
55
54
|
- Each seller and the customer (if new relationship)
|
|
56
55
|
6. **Finalize** — Inventory is reserved, payment is authorized, and the `order_group.created` event is emitted
|
|
57
56
|
|
|
58
57
|
<Info>
|
|
59
|
-
|
|
58
|
+
A single payment collection is shared across all of a cart's split orders and stays on the **cart**, not on each order. Split orders are **not** linked directly to the payment collection (Medusa's `order ↔ payment_collection` link is one-to-one on the payment-collection side). Read the payment collection through the cart:
|
|
59
|
+
|
|
60
|
+
```text
|
|
61
|
+
order → cart → payment_collection
|
|
62
|
+
```
|
|
63
|
+
|
|
64
|
+
Order-group and vendor order reads normalize `cart.payment_collection` back onto `payment_collections` and recompute `payment_status` from it, so consumers keep the familiar shape. When requesting fields on vendor order routes, make sure the request does not replace route defaults that already include `cart.payment_collection.*` (a `fields=` list containing bare fields replaces defaults in Medusa; use `+`-prefixed fields to merge, or include the `cart.payment_collection.*` paths explicitly).
|
|
60
65
|
</Info>
|
|
61
66
|
|
|
62
67
|
## Events
|