cartpresets_settings. Preset and item settings live in their own tables.
Store settings
Carrier product
The hidden product custom items ride on. See The carrier product.
Cart behavior
invalid_item accepts skip, none or backorder. unavailable_action accepts leave, deactivate or redirect. post_add accepts cart, checkout, stay or custom.
Cart notices and labels
Only the ones you have rewritten are stored. See Cart notices and wording.
Links and fallbacks
Data control
See Data and uninstall.
Preset settings
Set in the editor, on one preset.redirect and clear_cart accept global to follow the store setting.
Item settings
Set on one item inside a preset.disc_type accepts none, pct, fixed or custom.
What “Pro to edit, honoured on both” means
Some settings can only be set on Pro, but are enforced on both builds. Purchase limits are the clearest case. Setting a cap needs Pro. Counting claims against one, and refusing a link once it fills, happens on both — because moving to the free build must never put a sold-out link back on sale. The same logic covers schedules. The general rule: honour the restriction, drop the enhancement.Where settings are stored
Writes walk the schema rather than the request, so a key that is not in the schema is never persisted no matter what a request contains. Developers can register their own keys — see the hooks reference.