This system is a modular web-based platform for managing virtual product sales, deliveries, and transaction tracking. It is designed for merchants in Second Life.

• Product catalog management
• Transaction history and manual logging
• Redelivery of purchased items
• Customer purchase lookup
• Vendor control and product assignment
• Delivery box registration and cleanup
• Script-accessible product browsing
• Automatic transaction recording via HTTP

Merchants can:

• View all products in a table
• Add, edit, or delete products
• Deliver products manually to customers
• Assign products to vendors

Each product includes:

• Name, version, price
• Permissions (copy, modify, transfer)
• Creator and image UUID

Merchants can:

• View all past deliveries
• Add new transactions manually
• Delete incorrect entries
• Redeliver products to previous buyers

Each transaction stores:

• Product name, quantity, price
• Sender and recipient info
• Source, location, and timestamp

Merchants can:

• Search for a customer by name
• View all products delivered to them
• Redeliver any item with one click

Merchants can:

• View all registered vendors
• Assign products via dropdown
• Send commands to vendors:
  • online / offline
  • refresh / mark / hovertext
  • changeproduct

Each vendor includes:

• Region, position, product, price
• Image preview and creator info

Merchants can:

• View all delivery boxes
• See region, position, and creator
• Delete boxes from the system

External systems can:

• Send GET requests to record transactions
• Include product, payer, receiver, and payment info
• Automatically store the transaction in the merchant’s database

This guide explains how merchants use the “My Vendors” interface to manage in-world vendor objects, assign products, and send commands to update their behavior.

The “My Vendors” page displays all vendor objects registered by the merchant. Each vendor includes:

• Region and position
• Product name and image
• Price
• Action buttons for remote control

Each row in the vendor table shows:

• Region – the simulator name
• Position – coordinates in-world
• Picture – product image (UUID-based)
• Product – currently assigned product
• Price – listed price in L$
• Actions – buttons to control the vendor

To assign a new product to a vendor:

• Use the dropdown menu in the Product column
• Select a product from your catalog

Each vendor can receive the following commands:

🟢 online – mark vendor as active

🔴 offline – mark vendor as inactive

♻ refresh – reload vendor state

❗ mark – highlight or flag the vendor inworls

hovertext – update hover text display

To send a command:

Click the corresponding button in the Actions column

To remove a vendor:

Click the 🗑️ Delete button

Confirm the prompt

The vendor is deleted from your database

This does not affect the in-world object directly.

This guide explains how merchants use the “My Delivery Boxes” interface to view and manage their in-world delivery boxes.

The “My Delivery Boxes” page displays a list of all delivery boxes registered by the merchant. Each box includes:

• Region and position in-world
• Creator name
• A delete option

Boxes are stored in the merchant’s personal `boxes.db` file.

Each row in the table shows:

• Region – the simulator name where the box is located
• Position – the coordinates of the box within the region
• Creator – the name of the avatar who created the box

This view helps merchants track where their boxes are placed.

To remove a box from the list:

• Click the 🗑️ Delete icon next to the box
• A confirmation prompt will appear
• If confirmed, the box is removed from the database

This action does not affect the in-world object directly — it only removes the entry from the merchant’s system.

This guide explains how merchants use the “My Products” interface to manage their product catalog, deliver items to customers, and edit or remove listings.

The “My Products” page displays all items listed in the merchant's product database. Each product includes its name, version, price, image, permissions, and creator. Merchants can:

• View all products in a table
• Deliver any product to a customer
• Edit or delete product entries
• Add new products via a separate form

When the page loads:

• All products are shown in a table with the following columns:
  • Product ID
  • Name and version
  • Price (in L$)
  • Image preview (from Second Life UUID)
  • Permissions: ✅ or ❌ for copy, modify, transfer
  • Creator name
  • Action buttons: ✏️ Edit, 🗑️ Delete, 📦 Deliver

To deliver a product:

• Click the Deliver button next to the product
• A prompt appears asking for the recipient's name
• Once entered, the product is sent to all delivery boxes listed in `user_<merchant>_boxes.db`

Success and failure counts are displayed after delivery

To update a product:

Click the ✏️ Edit icon next to the product

Modify fields like name, version, price, image, permissions

To remove a product:

Click the 🗑️ Delete icon next to the product

A confirmation prompt appears

If confirmed, the product is deleted from the database

To add a new item:

Click the ➕ Add New Product button

You’ll be redirected to a form:

Fill out the form with:

Product name and version

Price

Image UUID

Permissions (copy, modify, transfer)

Product images are loaded from Second Life using the UUID stored in productpicture

Delivery boxes must be configured before delivery works

All actions are performed per merchant

This guide explains how merchants and external scripts interact with the delivery and transaction system. It covers redelivery, transaction management, customer lookup, and product access.

To view your transaction history:

• Open Transactions
• You’ll see a paginated list of all deliveries made
• Each row shows:
  • Product name
  • Recipient name
  • Quantity and price
  • Delivery source and location
• Use the ➕ Add Transaction form to manually log a sale
• Use 🗑️ Delete to remove a transaction
• Use 📦 Redeliver to resend a product to the original recipient

Fill out the form:

• Required fields:
  • Product name
  • Recipient name
  • Recipient UUID
  • Merchant name
  • Merchant UUID
• Optional fields:
  • Quantity
  • Gross / Net / Received amounts
  • Location and source

Once submitted, the transaction is stored and appears in your history.

To view what a customer has purchased:

• Enter the customer’s name (case-insensitive)
• You’ll see a list of all products they’ve received
• Each product includes a 📦 Redeliver button

This tool is useful for support, refunds, or re-delivery requests.

Redelivery is available in multiple places:

• redeliver any past transaction
• redeliver based on customer name
• search all merchant databases

This guide explains how merchants use the Transaction History interface to view, manage, and redeliver past deliveries. It also covers manual transaction entry and pagination.

When the page loads:

• Transactions are displayed in a paginated table
• Each row shows:
  • Date of delivery
  • Product name
  • Quantity
  • Received amount
  • Source and location
  • Sender and recipient names

Use the ⬅️ Previous and ➡️ Next buttons to navigate between pages. Each page shows up to 15 transactions.

To manually log a delivery:

• Fill out the Add Transaction form at the top
• Required fields:
  • Product name
  • Recipient name
  • Recipient UUID
  • Merchant name
  • Merchant UUID
• Optional fields:
  • Quantity
  • Gross / Net / Received amounts
  • Source and location (default: Manual / System)

Once submitted:

• The transaction is saved to the database
• It appears immediately in the transaction list
• Redelivery becomes available for that entry

To resend a product:

• Click the 📦 Redeliver button next to any transaction
• The system sends a POST request to all delivery boxes listed in `user_<merchant>_boxes.db`

Success and failure counts are displayed after delivery

To remove a transaction:

Click the 🗑️ Delete button next to the entry

A confirmation prompt appears

If confirmed, the transaction is permanently deleted

This is useful for correcting mistakes or removing test entries.

The transaction list is paginated:

Default: 15 entries per page

Total pages are calculated automatically

This endpoint records a transaction using data provided via a GET request.

• Only accepts GET requests for registered merchants
• URL: https://mond-keks.de/slvendors/ans.php

The following parameters can be passed via the query string:

• `TransactionID` – unique identifier for the transaction
• `ItemID` – internal product ID
• `ItemName` – name of the product
• `MerchantName` – name of the merchant
• `PayerName` – name of the paying customer
• `PayerKey` – UUID of the payer
• `ReceiverName` – name of the recipient
• `ReceiverKey` – UUID of the recipient
• `PaymentGross` – total amount paid
• `Location` – delivery source (e.g. In-World or Marketplace)

Returns a confirmation message:

✅ Transaction recorded for ReceiverName

These are potential features and improvements to expand the system’s capabilities:

• 📊 Sales Analytics Dashboard
  • Visual charts for revenue, top-selling products, and customer activity
  • Filters by date range, product, or region

• 📦 Box Health Monitoring
  • Periodic ping to delivery boxes to check online status
  • Visual indicators for offline or unreachable boxes

• 🔐 Role-Based Access
  • Allow assistants or team members to manage products or transactions
  • Define permissions per user (e.g. view-only, redelivery, full access)

• 📁 Product Categories and Tags
  • Organize products by category (e.g. clothing, furniture, scripts)
  • Enable filtering in the product list and script APIs

• 📜 Transaction Export
  • Export transaction history as CSV or JSON for accounting or backup