Designing a shared WooCommerce cart customers can review with confidence

A shared cart helps when someone else needs to review the order: a customer sends a selection, a colleague prepares a product proposal, or a household discusses the contents. The strongest flow lets the recipient inspect the proposal before deciding what happens to the current cart. Yindle Share Cart builds that decision around an expiring, revocable link.

Start with the receiving customer

A link is not an instruction to overwrite the current cart without a choice. The recipient should see current prices and availability and explicitly choose whether to replace or merge. That matters for a guest who already has items in the cart, and for a signed-in customer with a saved cart. Sharing and importing do not require an account; named saved carts are available to signed-in customers.

Make the preview useful

Show the proposed items, quantities, and totals in the review view. A printer-friendly view can include items, SKUs, quantities, discounts, totals, and print date. Current availability remains authoritative: a shared snapshot is context for a new order, not a promise that stock or price will stay unchanged. Test an expired link, a changed product, and a cart containing a coupon or configuration.

Plan for both WooCommerce renderers

Share Cart supports the classic cart and the native Cart Block. The server checks and import rules are shared, while controls render in their respective locations. After a WooCommerce fragment refresh, verify that the controls return. On mobile, preview, replace, and merge must remain easy to distinguish. Use concise copy that explains the consequence of each choice, especially when the current cart is not empty.

Give links a lifecycle

A share link should have an end date. The setting controls the finite lifetime, and a daily task purges expired records when no saved cart still refers to them. A saved cart is a different relationship from a public link. Include deleting, resharing, and checking old links in your operating process. The default privacy choices preserve data on deactivation and uninstall until an administrator explicitly enables cleanup.

Make sharing understandable

Explain in your store copy what the recipient receives and what may still change. A share link contains a proposal; the recipient gets a new cart review. Avoid wording that suggests reserved stock, a fixed price, or a completed order. Tell support how a customer should report an old link and when resharing is the right answer. This turns the technical expiry date into a clear customer expectation.

Check integrations before launch

Staging should cover at least a classic cart, a Cart Block, two independent guest sessions, a signed-in saved cart, and an existing share link. Add a configurable Kit if you share configurations: Yindle Kit Configurator keeps selected products as their own order lines. If your first priority is a calmer order path, see Yindle Checkout . The current Share Cart product page covers installation, settings, and boundaries without making a stock or price promise.

Previous insight
Next insight

Start with your question

Where does your team get stuck?

Your first enquiry does not need to be a technical brief. Tell us which systems you use and where work gets stuck. Together we discuss what is possible and which step you can take next.

Discuss my project