bean.Start with the problems that cost you every day.
Bean's live modules target four everyday operational problems. Each one is solved inside the same organisation, with the same roles and the same audit trail.
One stock list your whole team works from.
Replace the shared spreadsheet with an inventory that belongs to your organisation. Every item has a unique SKU, a quantity and its own unit. Search the current page, page through the full list on the server, and add or edit items in place.
- Duplicate SKUs are rejected before they cause confusion.
- Items with no stock are flagged as None on hand.
- Writes to a suspended organisation are refused.
Your point of sale and your stock count, in agreement.
Connect a point-of-sale system or online store as an integrated application. Each completed sale it reports deducts stock from the matching SKU, records the transaction and, where your organisation has a commission rule, the commission.
Connections use Bean's documented event API; there are no ready-made connectors for specific POS brands yet.
You choose what happens when stock runs short: require intervention (the default), allow negative stock, or record the sale without deducting stock. The policy in force is saved with every sale.
The right people, in the right organisation.
Add existing accounts to your organisation as owners, administrators or members. Owners manage everyone; administrators add and remove members; members can leave. Every organisation keeps at least one owner.
What someone can do inside a module comes from their account permissions. New accounts start with none until an administrator grants them.
A record you don't have to reconstruct.
Bean writes inventory changes, membership changes, sign-ins and integration lifecycle actions to an audit log that the database keeps append-only. Each integrated application also has its own audit history: registered, subscriptions changed, activated, suspended.
