Shop Project - Documentation

The Shopping Cart as a Purely Client-Side Organizational Tool

In contrast to classic B2C online shops, adding an item to the shopping cart does not trigger a server-side reservation or informational pre-booking against the seller's intent. Mechanically, the shopping cart operates as a local client-side storage (Session/LocalStorage).

Legally, this state is classified as a mere *invitatio ad offerendum* (invitation to treat) by the seller, pre-sorted by the buyer on their own terminal. At no point does a platform-driven offer or declaration of intent exist.

Function of Checkout: Intent Dispatching instead of Conclusion

Clicking the "Send Purchase Intent" button (Checkout) does **not** trigger an electronic purchase contract. The system process is defined as follows:

Workflow: Client Cart ➔ JSON Payload ➔ Injection into encrypted P2P chat ➔ Manual negotiation.

The system merely transforms the local structure of the shopping cart into a standardized text package injected as an opening message into a bilateral chat room. The actual binding contract conclusion occurs exclusively through the **explicit, manual agreement of both users** within this private space. Due to Zero-Knowledge encryption (AES-256-GCM), the platform has knowledge of neither the conclusion nor the failure of these negotiations.

Complete Disclaimer of Warranty and Liability

Since the operator acts not as an intermediary but as a pure infrastructure provider (comparable to a physical bulletin board), the following boundaries apply:

• No Performance Guarantee: The operator is not liable for non-delivery, defects in goods, or fraudulent intent of either party.
• No Regulatory Reporting Obligation (DAC7 / PStG-E): Because the system processes no payments (no escrow) and logs no central contracts, it does not qualify as a reportable platform under digital tax mandates. Transactions are exclusively archived encrypted within the private user account.