# shop

> Reference for the shop tool of Geenius MVP: shops, orders, payments status, readiness and vouchers, with every action.

Source: https://mvp.geenius.io/docs/reference/shop/

A shop is a web app of kind webshop. Make it with apps create (a preset such as bakery-shop), put products in the catalog, publish with apps publish, and change settings with apps kit_config. Any seat reads; a member seat moves orders along.

Call it as `geenius_mvp(tool: "shop", action: "<action>", args: {...})` through Geenius OS.

## Actions

| Action | What it does |
|---|---|
| `money` | The money per provider and currency. |
| `order_read` | One order in full. |
| `order_set_status` | Move an order along (fulfilment only): paid to ready, shipped or completed. |
| `orders_list` | A shop's orders, newest first. |
| `payments_status` | How payments run, with the exact environment names the keys go in. |
| `readiness` | What holds a shop back from going live, in the order to fix it. |
| `shops` | Every shop, its mode, payments and seller. |
| `test_order` | A whole test order through the built-in mock. |
| `voucher_redeem` | Redeem an amount of a voucher at the counter. |
| `vouchers_lookup` | A gift voucher by its code. |

> [!TIP]
> Ask for the exact arguments of any action with `action: "help", of: "money"`. The server answers from its own definitions, so that answer is always current.

> [!NOTE]
> Never invent prices: they come from the catalog and are recomputed on the server. Never mark an order paid, and never switch a shop to live: a person does, after readiness. Legal texts are templates, not legal advice.