Named shopping carts make repeat ordering useful when customers have several regular selections. A generic reorder previous order button is too crude in that situation. Names such as “Service Van North”, “Office Supplies” or “Project Delta” help users recognise the purpose, update the contents and only then place an order.
This approach mainly suits business customers with periodic orders, multiple locations or recurring project sets. The feature must not become a hidden subscription: customers consciously choose when to open, adjust and order from a list each time.
Use a shopping cart as an editable working list
A saved shopping cart differs from an order history or favourites list. An order shows what was definitively purchased in the past. Favourites contain individual products without quantities. A named cart stores a specific combination with quantities and possibly variants, intended as a starting point for the next order.
Let users enter a recognisable name and change it later. Show the last modification date, the number of lines and preferably a brief price indication, with a note that amounts are recalculated when the cart is opened. If business software also uses project codes or cost centres, decide whether that reference belongs to the list, the final order or both. The guide Reliably connecting your online store and ERP helps make that ownership decision explicit.
Choose a clear permissions model
| Model | Suitable for | Point to consider |
|---|---|---|
| Personal | Individual buyer | The list becomes hard to find when staff change |
| Shared by customer account | Small purchasing team | Define who can edit or delete |
| By branch | Organisation with multiple locations | Assign permissions to the correct branch |
| By project | Temporary project teams | Archive after completion and prevent list clutter |
Start simply. A personal list is straightforward both technically and organisationally. Sharing can be added later when ownership is clear. Ask for confirmation before deletion, but do not keep unlimited shadow copies. When an account is closed, saved carts must be deleted according to the chosen retention period.
Also prevent a list from quietly acquiring two versions. If two buyers open “Van West” at the same time, it must be clear which version was saved most recently. A simple warning showing the modification time and editor’s name is often better than silently letting the last saved version win. For larger teams, copying to a new name may be safer than overwriting a shared list.
Fictional example: three service vans
Technical management company Kopermolen has three service vans carrying different materials. Buyer Layla creates a named shopping cart for each van. Once a month she opens “Van West”, checks which parts are still needed and adjusts the quantities. A discontinued model is clearly marked. She chooses the replacement product herself and saves the updated selection under the same name.
The order receives the internal van number and cost centre only at checkout. This keeps the list reusable while the financial reference can differ for each order. Successful payment does not automatically empty the list: Layla decides whether the new selection replaces the existing version.
The final order is the source of truth for the data flow to administration or the warehouse. Yindle Connect can connect that order flow without temporary working lists unintentionally being treated as sales orders.
Checklist for repeat ordering without surprises
- Explain the difference between order history, favourites and a saved cart.
- Require a name and prevent empty or identical names where they cause confusion.
- Show when the list was last changed.
- Recheck products, variants, stock, prices and discounts when the list is opened.
- Show which lines could not be fully restored.
- Decide whether a list is personal, shared across the customer account, branch-specific or project-specific.
- Make editing, copying, sharing and deleting separate actions.
- Test how the feature behaves when a user account is deleted.
Then measure whether customers actually reuse lists. Many carts created but never opened may mean the feature is poorly explained or that order history already meets the need. Build extensive team management only when actual use justifies it.
When analysing use, also consider what happens after a list is opened. A list that is opened frequently but rarely ordered may contain outdated products, be difficult to edit or serve only as a comparison. Combine the numbers with brief conversations with buyers. The aim is fewer searches and fewer incorrect repeat orders, rather than simply increasing the number of saved carts.
Let Yindle design a repeat-order flow that suits your business customers.
For named carts, account-free sharing and saving for signed-in customers, see Yindle Share Cart ; also read how a shared cart is handed over.