Cart / wishlist

What it does

Behaviours, not fields. Choosing between two modules is choosing between these.

Kept per person and left alone. The value is that it is still there next visit, which is when a good share of considered purchases actually convert.

Records the price at the moment it was saved, so a rise since then is something the agent can raise rather than something the visitor discovers at checkout.

Availability is checked live, so a saved item that has sold out says so instead of leading to a dead end.

Works as a gift list: the same structure, shared by link.

How it works

1
Items are held against a person or an anonymous session and left alone.
2
The price at save time is recorded, so a change is something the agent can raise.
3
Availability is checked when the list is shown rather than when it was saved.
4
The list survives between visits, which is when considered purchases actually convert.

Best for

Reading and scanning. It is the right default more often than it looks.

Not the right choice for

Comparing many fields at once — use a table.

What a row holds

Every field, and what the agent listens for to fill it — which is the difference between a page you type into and one that fills itself.

Field	Type	Filled from
Itemrequired	text	A product a visitor picked out without buying, matched to the catalogue.
Addedrequired	text	How long ago, which is what makes a follow-up natural rather than creepy.
Price thenrequired	money	What it cost when saved. A rise since is a conversation the agent can open.
Still availablerequired	text	Checked live, so a saved item that sold out says so rather than leading nowhere.

What it does not do

A module chosen for something it cannot do costs more than one that was never offered.

No reservation — saving does not hold stock.
Anonymous lists are tied to a session and lost if it is.
No sharing unless it is used as a gift list.
No automatic notification on a price drop; the agent raises it when the person returns.

Before it works

What you have to provide, if anything.

Nothing.
Pair with Product catalog, which supplies the availability this checks.

In practice

A shop selling a 180-euro grinder that people think about for a fortnight.

“A visitor saved the grinder and the pour-over, then left without buying.”

What was said to the agent

What the agent built

Two items held against their anonymous session, with the prices as they stood that day.

What changed

They came back eleven days later. The agent opened with both still available and the grinder down to two — and had to be told none of it.

Better with

These do a different job on the same data. An agent can have all of them.

Product catalogLive

The business sells or recommends specific, nameable things — a shop, a maker, a gallery, a supplier with a range.

OrdersLive

Things are sold and then have to be prepared, shipped or collected, and several are in flight at once.

CouponsLive

Discounts are offered through codes and someone needs to see which ones worked and which are still live.

Questions

What data does the Cart / wishlist page use?

It reads list_item records the agent has collected. Chosen items to buy/keep. Nothing has to be imported first — the page appears once there is something to show.

Do I have to build or configure it?

No. You describe what you need in a sentence and the agent chooses the view and fills it. Custom pages exist for the cases no built-in view covers, and those are reviewed before they go live.

When is a list the wrong choice?

Comparing many fields at once — use a table. It is best for: reading and scanning. It is the right default more often than it looks.

Does it stay up to date?

Yes. The page is a view over the data rather than a copy of it, so anything the agent learns afterwards shows up without a rebuild or a re-import.