Product · after the price

A quote is only useful if it turns into work

Every quote lands somewhere you can act on it: an inbox with the part, the configuration and the buyer’s details together; an e-mail that arrives; a webhook your ERP can trust; or a line in the cart you already use.

Inbox

Quotes and enquiries in one place

Everything about the job, together

The part, viewable. The exact configuration and version that priced it. The breakdown. The buyer, their company, their previous jobs. No hunting through e-mail for the attachment.

Quotes you adjust and send

Override a line, add a note, set an expiry, send it as a PDF. The buyer accepts from a link, and what they accept is what you sent.

RFQs for what cannot be priced

A part your rules send to review, an oversized job, a material you want to discuss: the geometry is still measured and the file is still viewable, so you answer with a number instead of asking for the file again.

Order states that mean something

Received, in production, shipped, complete - with the buyer told at each step, in your name and from your domain if you want.

Callbacks

Webhooks you can actually verify

Every event - a model analysed, a quote created, an order placed, a configuration published, a quota threshold reached - can be delivered to your endpoint, signed with HMAC-SHA256 over the timestamp and the raw body. Verification is five lines, and we show it in six languages.

Retries are scheduled, not hopeful: one minute, five, thirty, two hours, six, twelve, then daily, with the whole delivery history visible and a replay button. Secrets rotate with an overlap, so you are never asked to swap a secret at the exact instant a delivery arrives.

And you are not expected to watch any of it. We write to you when a delivery gives up, when an endpoint has been failing for three days - four days before we switch it off - when we do switch it off, and once a day about everything that did not arrive. Every one of those messages says the same thing, because it is the thing worth knowing: the order is in your inbox either way.

Webhook reference and the verification snippets →

Carts

When checkout lives somewhere else

If you already sell through WooCommerce, a configured part becomes a line in that cart at the quoted price; with the Shopify app, which has not yet been run against a real store, it becomes a draft order. Either way your existing payments, taxes, shipping and accounting keep working and nothing has to be entered twice.

Taking payment inside the widget, through Stripe Connect straight to you, is planned and not built yet. We never hold your customers’ money.

Integration guides → · Cart recipes in Node, PHP and Python →

No code at all

If your process is e-mail, that is a valid process

Set one address and every order and request for quote arrives there with its lines, the total and a link to the part in your console. A Zapier connection is not built yet; a webhook can feed a spreadsheet, a Slack channel or your own job board in the meantime. Plenty of excellent shops run on a shared inbox, and Quotometry does not require you to stop.

See a quote arrive

Place one in the demo shop and watch what a merchant gets.