MSP Store

The problem

A client emails asking for fifteen laptops. Someone looks up cost in the distributor portal, applies whatever markup they remember, types a quote, and waits. The client replies asking for the same thing in a different configuration. Two weeks later nobody can say what margin the deal carried, and the invoice was raised by hand from a packing slip.

Meanwhile the client has no way to see what you sell, no way to see the price they have negotiated, and no record of what they have already bought from you.

What Solidlio does about it

Your store is your slice of a shared distributor catalogue plus the products and services you author yourself. A pricing profile turns cost into a sell price — a base multiplier, per-category and per-brand markup, a minimum-margin floor and a rounding rule — and per-client rules layer negotiated contract prices, volume breaks and discounts on top of that. One engine computes every line price, so the product page, the cart and the placed order all charge the same number.

Clients browse and order in their own portal. Every order arrives PENDING_APPROVAL, you approve or reject it, advance it through PROCESSING → SHIPPED → DELIVERED with carrier and tracking, and delivery is what triggers the invoice — automatically, once, on your net terms.

Capabilities

Built for MSPs and their clients

Your account holds many client organizations. Account-level scoping alone is not isolation for a buyer, so the store enforces two separate rules — one on what a buyer can see, one on what a buyer can reach.

How it works

1. Set the markup once — a base multiplier on cost, category and brand overrides, minimum-margin floors, and a rounding rule. Add a currency buffer if you buy in a currency you do not sell in.
2. Curate what you sell — block the distributors you do not use, hide the products you do not want quoted, and add your own items for anything the catalogue does not carry.
3. Price the client — a contract price, a percentage off, or a volume break, scoped to that one organization.
4. The client shops — faceted browse in their own portal, at their own price, with cost and margin never leaving your side of the boundary.
5. The order arrives for approval — server-priced from item ids and quantities only; a price in the request is rejected outright.
6. You fulfil it — approve, then advance through processing, shipped and delivered, recording carrier and tracking as you go.
7. It invoices itself — the delivered order is picked up on the next invoicing run and billed on its net terms, exactly once.

Numbers that are enforced, not suggested

• Prices are never accepted from the client. The checkout schema is strict: item ids and quantities only.
• Stale exchange rates stop a sale rather than mispricing it. A rate older than the freshness bound makes the line unavailable; checkout refuses the order.
• Unresolvable tax is held, never guessed. The order is flagged with a [TAX HOLD] note and jurisdiction-specific guidance instead of shipping at $0 tax.
• Fulfilment is forward-only. Delivered and cancelled are terminal; shippedAt and deliveredAt are stamped once, on first crossing.
• A client with no organization context is refused, not defaulted.

Editions

The store carries one plan gate: control over which distributors you may block. The storefront, pricing profiles, custom items, bundles, orders, fulfilment and invoicing are available on every tier.

A refused block returns the tier required, so the upgrade can be offered in place rather than as a dead end.