Items represent what’s inside the shipment. My current thinking is to have them serialized ala adjustments, each ShipmentItem is a value object that has a purchased entity type, purchased entity id, quantity. We also talked about storing an order item ID but at this point I’m no longer convinced it’s necessary. Might just need a use case for it though.
The reason why I want to serialize items is because they’re going to be recalculated during the refresh. If our default behavior is “single shipment per order”, then each change to the order (at cart/checkout) must be reflected in the shipment.
The amount is a price field, taken from the selected rate. Adjustments store handling fees and/or taxes.
Comment | File | Size | Author |
---|---|---|---|
#4 | shipment.patch | 27.11 KB | bojanz |
Comments
Comment #2
TylerMarshall CreditAttribution: TylerMarshall at Acro Commerce commentedCurrently tracking progress on my fork of Bojanz branch
https://github.com/Tigatok/commerce_shipping-1/tree/2831602/create-a-shi...
Comment #4
bojanz CreditAttribution: bojanz at Centarro for Adapt commentedHere is jsacksick's current progress. I'll wrap the patch up and commit it.
Comment #6
bojanz CreditAttribution: bojanz at Centarro for Adapt commentedDone.