Перейти к содержимому

Quote requests

Это содержимое пока не доступно на вашем языке.

Made-to-order products rarely sell through a cart because the price depends on the configuration, the quantity and often the project. Quote requests handle this without any store integration. The visitor configures the product, presses the button in the summary and leaves their contact details. The full configured selection arrives in your inbox with their email as reply-to.

Шаг 1/7

Товары под заказ редко продаются через корзину, потому что цена зависит от конфигурации, объёма и часто от проекта. Запросы предложений делают каналом продаж сам конфигуратор.

Запросы предложений: продажа без корзины
Шаг 1 из 7
  1. Товары под заказ редко продаются через корзину, потому что цена зависит от конфигурации, объёма и часто от проекта. Запросы предложений делают каналом продаж сам конфигуратор.
  2. Откройте настройки конфигуратора. Здесь собраны настройки уровня товара.
  3. Для настройки достаточно включить один переключатель. Код, вебхуки и CRM не нужны. Кнопка одинаково появляется в опубликованном конфигураторе, в отдельном просмотрщике, в ссылках для отправки и в коде встраивания.
  4. Назовите кнопку так, как принято у вас, например «Узнать цену» или «Запросить расчёт». Если оставить поле пустым, каждый посетитель увидит надпись на своём языке. По-русски это «Запросить цену».
  5. Так опубликованный товар видит посетитель: он собирает конфигурацию, а затем открывает сводку по ней.
  6. Кнопка запроса стоит в сводке, рядом с конфигурацией, которую она передаст: описывать товар словами посетителю не нужно.
  7. Имя, e-mail, при желании телефон и сообщение. Письмо приходит вам, а ответ уходит прямо на e-mail посетителя. Во вложении находятся изображение собранной конфигурации, список деталей с SKU и ссылка, которая открывает эту же конфигурацию.

Open your project’s Configurator tab and switch on Quote requests in the settings column. Optionally set your own button label, such as “Get a price” or “Request an offer”. The default is “Request a quote”. Publish as usual.

No code, webhook or CRM is required. The button now appears in the published configurator’s summary, in the standalone viewer, in share links and in the embed.

The summary gains a button. Pressing it opens a short form with name, email, optional phone and message. The configured selection (every part, chosen variation and SKU) is attached to the request automatically, so the visitor does not describe the product by hand. Sending the form is the consent step. The visitor is told their contact details go to you, the seller.

Every request lands in two places: your inbox, and the panel.

An email per request, containing:

  • the visitor’s name, email (set as reply-to, so you can answer by replying), and phone if given,
  • their message, if any,
  • an image of the configured product exactly as the visitor saw it, attached to the mail,
  • the configured selection as a part-by-part list with SKUs,
  • the price of each row and the total the visitor saw, when your page shows prices,
  • a link that reopens the exact configuration in the viewer.

Repeated submissions of the same configuration by the same visitor within a few minutes are collapsed into one request.

Leads in the panel sidebar lists every request the workspace has received, with contact details, project, message, the date, and a link that reopens the exact configuration.

  • Status: each request moves through New → Contacted → Won, or is marked Spam. The tabs above the list filter by status and by project.
  • Export CSV: hand the current view to your sales team or import it into your CRM. The export follows the filters you have applied.
  • Bulk delete: select rows and delete them in one step. Reserved for the workspace owner and admins.

Requests are kept for 90 days and then permanently deleted. Export what you need to keep, or treat your CRM as the long-term record.

Leads → Webhook posts every new request to an HTTPS endpoint of your choice as JSON. Connect it to Zapier, Make, or your CRM directly. There is no connector to install, and the lead stays in the panel either way.

The request carries the visitor, the project, the SKUs and the configuration link:

{
"event": "lead.created",
"email": "[email protected]",
"name": "Ada Visitor",
"phone": "+90 555 000 0001",
"lead": {
"id": 1042,
"name": "Ada Visitor",
"email": "[email protected]",
"phone": "+90 555 000 0001",
"message": "Need a quote for the corner unit",
"locale": "en",
"created_at": "2026-08-15T10:00:00+00:00",
"configuration_url": "https://model.togenar.com/?project=...",
"skus": ["OSLO-BODY-WALNUT", "OSLO-LEGS-CHROME"],
"selection": [{ "partLabel": "Body", "label": "Walnut", "sku": "OSLO-BODY-WALNUT", "price": 1290 }],
"displayed_price": { "total": 1890, "currency": "EUR" },
"rules_check": { "verdict": "valid", "violations": [] }
},
"project": { "id": "...", "name": "Oslo sofa" },
"workspace_id": "..."
}

Prices travel with a request when your page passes them to the viewer with setPrices and a three-letter currency. They are the figures the visitor saw on your page. displayed_price is null when no price was shown. The panel lists the same prices per request and totals them per currency for requested and won leads.

Verify every call. When you save the endpoint we show a signing secret once, so store it. Each request carries X-Togenar-Timestamp and X-Togenar-Signature: sha256=…, the HMAC of timestamp.body:

const expected = 'sha256=' + crypto
.createHmac('sha256', process.env.TOGENAR_WEBHOOK_SECRET)
.update(`${req.headers['x-togenar-timestamp']}.${rawBody}`)
.digest('hex');
if (expected !== req.headers['x-togenar-signature']) return res.status(401).end();

Requirements and behaviour:

  • The endpoint must be a public https:// address. Private, loopback and internal addresses are refused, and redirects are never followed.
  • A failed delivery is retried before it is given up on.
  • The last delivery attempt and its HTTP status are shown next to the setting.
  • Only the workspace owner and admins can set or change it.

To protect your inbox from an abnormal traffic spike, an unusually large number of requests in one day arrives as a single summary email that evening instead of one mail each. Everything is still recorded and listed under Leads, and the Leads page tells you when that has happened. Nothing is dropped.

Quote requests and add to cart serve different selling models, and the configurator does not show both by default. When AR Add to Cart is on, the cart owns the conversion step and the quote request button is hidden. If your catalogue needs both, with standard items going to the cart and made-to-order items to a quote, switch on Show alongside a cart next to the Quote requests toggle.

Hosts that want to handle the enquiry themselves can keep using the enquire embed attribute and event. The event still fires with the toggle on.