summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorThien-Thi Nguyen <ttn@gnuvola.org>2021-08-10 23:28:19 -0400
committerThien-Thi Nguyen <ttn@gnuvola.org>2021-08-10 23:28:19 -0400
commit108101d5c13e2e1e1e12290c29a53969ce715511 (patch)
treef0fdde3bf03899c6c2b6cabfd18359c74724db1f
parentea3a137a097c03c8b4877a855197797d61c882d4 (diff)
downloaddocs-108101d5c13e2e1e1e12290c29a53969ce715511.tar.gz
docs-108101d5c13e2e1e1e12290c29a53969ce715511.tar.bz2
docs-108101d5c13e2e1e1e12290c29a53969ce715511.zip
add para on "limited stocks" -> use product locks; mention order locks and auto-unlocking
-rw-r--r--taler-merchant-manual.rst7
1 files changed, 7 insertions, 0 deletions
diff --git a/taler-merchant-manual.rst b/taler-merchant-manual.rst
index 4a9fd7a..1be0c7c 100644
--- a/taler-merchant-manual.rst
+++ b/taler-merchant-manual.rst
@@ -194,6 +194,13 @@ actors claiming orders is problematic (say because of limited stocks). The use
of claim tokens is optional, but if a claim token is used, it must be provided
to the wallet as part of the order URI.
+Additionally, when stocks are limited, you can configure Taler to
+set a *product lock* on items (say, while composing the shopping cart).
+These locks, as well as the *order lock* (when the order is complete),
+can be configured to auto-unlock at a certain time or triggering event.
+
+.. FIXME: Is the "or event" correct? If so, what events are triggers?
+
A wallet may *pay* for a claimed order, at which point the order turns into
a (paid) contract. Orders have an expiration date after which the commercial
offer expires and any stock of products *locked* by the order is released,