MSP Store

A branded storefront your clients buy from, priced by rules you set once, with every order landing in your approval queue and invoicing itself on delivery.

How Solidlio helps

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

Capabilities — reference table
CapabilityWhat it does
Markup profilesTurn distributor cost into a sell price with a base multiplier plus per-category and per-brand overrides.
Minimum-margin floorsRaise any price a markup would leave below the gross margin you set for that category or brand.
Price roundingFinish every computed price at .99, .95, the nearest dollar, the nearest cent, or not at all.
Per-client pricingContract prices, percentage discounts and volume breaks scoped to one client organization.
Best-price resolutionTwo client discounts never compound — the single best applicable rule wins, deterministically.
Catalogue curationSet any catalogue product to visible, hidden or approval-required for your store.
Vendor controlAllow or block distributors for your store, with an optional per-vendor markup.
Custom itemsAuthor your own products and services with SKU, price, images and attached documents.
BundlesSell a group of items at a fixed price that expands server-side into its priced components.
Client storefrontFaceted browse, product detail, cart and checkout in the client’s own portal, at that client’s price.
Order approvalEvery client order lands in your queue; approve or reject with a reason before anything is committed.
Fulfilment trackingForward-only PROCESSING → SHIPPED → DELIVERED with carrier and tracking, and timestamps stamped once.
Automatic invoicingDelivered net-terms orders raise their invoice on a scheduled run, idempotently — never twice.
Client spend analyticsMonthly spend, order counts and top products, for the client’s own organization only.
AI order triageSummarize and assess an incoming order on demand, stored on the record.

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.

Built for MSPs and their clients — reference table
Organization (the client)MSP
Cost and marginCost price, margin and vendor markup are stripped from every catalogue, item and order payload.Visible on every catalogue and pricing screen.
Markup policyNot visible.Owns it; applies account-wide, overridable per category, brand, vendor.
Negotiated pricingSees its own price, not the rule that produced it.Sets contract, discount and volume rules per client organization.
CatalogueSees only what the MSP has made visible.Sets per-product visibility; blocks whole distributors.
OrdersSees only its own organization’s orders. Fails closed without one.Sees every order in the account; approves, rejects and fulfils.
SpendIts own spend history and top products.Account-wide store statistics and booked revenue.
InvoicingReceives one invoice per delivered order on agreed terms.Terms set per order; invoicing runs itself.

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.

Plans and access

Availability depends on your plan, role and account permissions. Capacity limits and service terms apply. Compare current plans and integration requirements, or ask us about your setup.

Sell your clients what you already buy for them, at the margin you meant to charge.

See this working on a real account.

Book a walkthrough and we will run this capability against your own clients, devices and tickets.

Book a demo All features

A walkthrough focused on the IT work you manage.