Stock that reorders itself.

Most invoicing tools track inventory the way they track customers — a list with a name and a number, disconnected from anything else. Stock count goes down on the spreadsheet, the supplier email gets sent manually, the invoice goes out on Tuesday. Three systems, three sources of truth, three places to forget to update.

Guliel ties stock to invoicing on one side and to suppliers on the other. When the count drops, the supplier order gets drafted. When the supplier invoices back, the count goes back up. The loop closes without you in it.

What ships when — Logistics (catalog, SKUs, stock levels, the stock-movement log) is live today, and so is the Automations engine that powers the auto-reorder loop below (stock drop → supplier order drafted → supplier invoice back → expense → report). The Logistics trigger (stock below threshold) fires today; wire it to a supplier-order action in the Automations editor and the loop runs. (Fully unattended email-send is rolling out — email.send is still a stub; draft-and-approve works now.)

How it works

The catalog is the spine. Every item — a product SKU, a service, a digital good — is an entry with optional default price, optional default currency, and optional quantity. "Optional" matters here. A consulting hour has no quantity (infinite supply). A widget has both a price and a count. A custom job has neither and the user enters everything on the invoice.

One catalog, two ends

The same catalog drives both the customer side and the supplier side. On an invoice you pick from your items — quantity gets deducted from stock. On a supplier order, you pick from the same catalog (plus the supplier's own published items, if they're on Guliel) — quantity gets added back when the supplier invoices the order.

Every quantity change writes a StockMovement record — type (manual add, manual set, invoice deduct, invoice restore), delta, before, after, who did it, what reference document. Audit trail for free.

Stock thresholds → auto-reorder

Each item can have a low-stock threshold. When the on-hand quantity falls below it, the automation engine fires. A typical automation: draft a supplier order to the linked supplier, restock quantity = order quantity, currency = the supplier's currency. You approve and send, or set the rule to auto-send if you trust it. Both the threshold (Logistics) and the Automations engine that turns it into an action are live — stock below threshold is emitted today, so this wiring is a few clicks in the Automations editor.

Auto-reorder, end-to-end (the design preview)

Concrete numbers, for what the finished loop looks like. You sell Widget A — SKU WDG-A, $25.50 unit, threshold 50. A customer order goes out with quantity 60. Stock was 100. Stock is now 40. The automation triggers, drafts a supplier order to your widget supplier for 200 units at the supplier's contracted price, sends it. Days later, the supplier issues an invoice against that order — quantity restored to 240. The expense lands. The report at the end of the month shows revenue from the customer invoice, COGS from the supplier expense, and the stock balance ending the period.

That's the whole loop, automated — three features, one transaction. The supplier flow, invoicing, and Logistics halves are live today, and so is the trigger-to-action piece in the middle: the Automations engine is live in production. Build the rule once and the loop runs unattended (with email delivery rolling out — draft-and-approve works today).

Inventory across organizations

If you run multiple orgs (manufacturing arm + sales arm, two country entities, parent + subsidiary), stock is org-scoped. Each org has its own catalog. An item in one org doesn't bleed into another. When two of your orgs trade with each other through the supplier flow, the count moves cleanly between them — out of one org's stock, into the other's, with the receipt and invoice on file in both.

What we don't do

We're not a warehouse management system. No barcoded picking, no bin locations, no wave-picking. Stock is per item per org. If you need bin-level inventory, run a real WMS and feed the totals into Guliel for invoicing.

Pricing

Logistics is included on every tier. The number of items and stock movements isn't metered. What you pay for is invoices, expense scans, reports, and automations — see /pricing. Free tier is fine for a freelancer selling a few products. Standard ($20 / org / month) unlocks unlimited automations, which is where logistics gets fun.

FAQ

Can stock go negative?

Yes. Backorders happen. We don't block an invoice when the count would drop below zero — the invoice issues and the count goes negative, with a warning toast in the UI and a flag on the item. You restock and the count climbs back. We treat blocking as the worse error: an unissued invoice loses revenue, a negative count is a number on a screen.

What about services, hours, or anything without finite stock?

Leave the quantity field empty when you create the item. The catalog displays ∞ for infinite supply. Invoices using that item don't trigger deductions. Most consulting and agency line items live here.

Do invoice deletions restore the stock?

Yes. When an invoice is deleted, the deducted quantity restores. The stock movement log records the restore with the invoice ID as the reference, so the audit trail shows the full life of the deduction. Credit notes handle partial restoration the same way.

Can I share my catalog with my buyers?

Yes. Items in your catalog have an "available for external order" flag. When you flip it on, customers who have you as a supplier in their Guliel account see those items when they build an order to send you. They pick from a list you control instead of typing free-form descriptions. The flag is per item — you publish what you choose, hide the rest.

Does Shopify or WooCommerce stock sync into Guliel?

Shopify integration on the roadmap pulls orders and the catalog into the logistics module. WooCommerce, similar. Until those ship, the API and the CSV import handle bulk catalog moves. We'd rather get the round-trip with suppliers right first, then sync the e-commerce side.

How granular is the stock movement history?

Per item, per movement, with the delta, the snapshot before and after, the user who triggered it, and the reference document if any. A typical item with a year of activity shows hundreds of entries — that's the data the inventory report reads from.

Start free at /pricing.