Customer rewards evaluation, not a local program claim
Customer rewards POS in Skadarlija, Belgrade: test the full value lifecycle
A business evaluating rewards in Skadarlija must prove identity, terms, earn, redeem, returns, privacy, accounting, security, recovery and measurement on the exact planned setup. A location name does not prove a complete rewards program, local approval or profitable outcome, and this page records no accepted local result.
What the pinned customer-rewards evidence establishes
These observations belong to the public v1.3.0 source boundary. They identify API behavior and missing controls for a trial; they do not prove that a rewards program has passed in Skadarlija.
A bounded points API exists
The pinned customer paths can initialize a balance, add positive integer points, redeem no more than the observed available balance and classify four tiers. This is source evidence, not an accepted counter workflow.
A balance is not a movement ledger
The reviewed mutation changes loyalty.points without a separate immutable earn, redeem, reverse, expire or adjust record linked to a sale, return, operator, reason and rule version.
Checkout automation was not established
The stable review did not establish a shipped cashier loyalty interface, automatic sale earning, receipt redemption or return reversal.
Program outcomes remain unproved
No accepted privacy flow, accounting treatment, restored ledger, fraud result or controlled experiment establishes a complete or profitable program in this location.
Unverified planning inputs for Skadarlija
Every value below is an unverified directory prompt, not an accepted configuration or market result. Replace it with current authority, observed behavior and retained evidence before issuing customer value.
| Control | Current planning input | Evidence required before rollout |
|---|---|---|
| Market and program scope | Skadarlija, Serbia | Named operating entity, site, objective, customer group, program owner, written terms and qualified local reviewers. |
| Value and accounting context | Serbian dinars; VAT | Approved point value, eligible consideration, redemption treatment, returns, expiry, outstanding obligation, estimates and reports. |
| Sale and payment candidates | cash, cards, bank transfers, QR payments and online payments | Completed-sale identity, authorization state, failed and pending payment, cancellation, refund and settlement evidence before value moves. |
| Workflow candidates | traditional restaurants, live-music dining rooms, cafes, wine bars and dessert counters | Accepted customer, cashier, manager, channel, branch, receipt, complaint and correction cases required by the operation. |
| Identity, purpose and preferences | No accepted result recorded | Minimum fields, duplicate and merge rule, enrollment terms, purpose, channel choice, objection, retention, access, correction, export and deletion. |
| Movement ledger and exceptions | No accepted result recorded | Immutable earn, redeem, reverse, expire and adjust entries linked to sale, return, actor, reason, rule version and before/after balance. |
| Security, concurrency and recovery | No accepted result recorded | Roles, approvals, unusual-activity review, atomic redemption, retry identity, branch conflict, disconnected behavior, export, backup and clean restore. |
| Incremental business result | No accepted result recorded | Predeclared baseline and comparison, gross-margin effect, reward, messaging, fraud and operating costs, complaints and stop rule. |
Run the 18-control loyalty acceptance path
Use synthetic customers, sales and returns in a disposable environment. A result is not accepted until movements reconcile, privacy and accounting owners sign their scope, and the restored records reproduce the same balances.
- Choose one measurable objective, baseline period and guardrail before collecting customer data or issuing value.
- Write customer-readable terms for earn, redeem, exclusions, stacking, returns, expiry, transfer, closure and complaints.
- Map the minimum identity fields, purpose, channel choices, retention, access, correction, export and deletion process.
- Create synthetic normal, duplicate, opted-out, insufficient-balance, high-value and closed-account customers.
- Run eligible and excluded sales, exact and insufficient redemption, failed payment, cancellation, full return and partial return.
- Attempt simultaneous redemption and interrupted retry; require one explainable result without duplicate value or a negative balance.
- Reconcile every movement to balances and approved accounting totals, export it, restore a clean device and reconcile again.
- Pilot with a predeclared comparison and expand only if incremental gross margin exceeds reward, messaging, fraud and operating cost.
Questions about customer rewards POS for Skadarlija
Does Posnic v1.3.0 include loyalty points?
The pinned customer API can initialize a balance, add positive integer points, redeem an observed available balance and classify bronze, silver, gold and platinum tiers. Seventy-two focused source tests passed, but no shipped cashier interface or automatic sale integration was established.
Does Posnic automatically award points after a sale?
Not in the reviewed stable evidence. Do not market or deploy automatic earning, cashier redemption or return reversal until the exact end-to-end cases pass.
Is Posnic customer rewards approved for Skadarlija?
No local approval or accepted program is recorded on this page. Named business, privacy, legal, finance, security and technical owners must approve retained evidence from the exact planned setup.
Can offline or cross-branch redemption be assumed?
No. Concurrent redemption, disconnected use, retry identity, branch conflicts and reconnect behavior were not accepted in the stable review.
Should loyalty members automatically receive marketing?
No. Program service and promotional messages can have different purposes, legal bases and customer expectations. Record purpose and channel choices separately and obtain local advice.
Do loyalty points create an accounting obligation?
They can, depending on the program and applicable framework. IFRS 15 includes customer-loyalty history, but a qualified accountant must determine the treatment, estimates and reports for the business.
What proves that a rewards program works?
No dashboard total proves causation. Use a baseline and a comparable holdout where lawful and practical, estimate incremental gross margin, and subtract reward, messaging, fraud and operating cost.
Primary product, privacy, accounting and research sources
Use the authorities responsible for the planned program. These sources establish product provenance and reusable acceptance questions; they do not replace current local privacy, marketing, consumer, security, tax, employment or accounting review.
Related location and workflow pages
These links are navigation only. They do not prove a Posnic office, customer, installation, accepted loyalty program, local support commitment or market approval.
Decision boundary for Skadarlija
Posnic can be downloaded and evaluated, but this page does not certify local enrollment, automatic earning, redemption, returns, marketing permission, accounting, security, concurrency, offline use, cross-branch behavior, recovery or profitable impact. Keep the result unverified until named owners approve retained evidence from the exact planned program.