Offers in Hummerce let a business customer - e.g. an installer, reseller, or distributor - prepare an offer for their own buyer, from their account: with the store's products, their own price, and a PDF document. Separately, an "Ask for an offer" form works on products the store doesn't sell off the shelf.
As of Hummerce 2.35 (customer offers and the "Ask for an offer" form: features older than 2.28; last changes to the module: 2.35.0), updated 2026-09-28.
¶ Benefits and use cases
- Offers for resellers - an installer, architect, or distributor prepares an offer for their own customer in the store and hands it over as a PDF.
- The reseller's own price (a discount, or, once enabled during implementation, a margin or markup) without exposing its calculation in the document for the buyer.
- Quote requests for non-standard products - the "Ask for an offer" form as a source of sales leads.
- Use cases: wholesalers and manufacturers selling through installers, construction, furniture, joinery, lighting.
- A logged-in customer creates an offer for their buyer in their account, from the cart's contents.
- The offer contains the customer's data, the buyer's data, line items with net prices before and after the change, and a total.
- The customer changes the buyer's price by one percentage for the whole offer - in the standard configuration this is a discount off the price. Calculating by margin or markup is available in the module and requires enabling during implementation.
- From the offer the customer generates a PDF document, and with the option enabled - Excel.
- From a saved offer the customer goes back to the cart: products from the offer go into the cart at the store's current prices, not the offer's prices.
- Offers can be restricted to selected store views (e.g. the B2B view only, see Views - several stores in one panel).
- The company manager sees the offers of employees (Company accounts and roles).
- For marked products, the product page shows an Ask for an offer button instead of Add to cart.
- The form collects contact details, preferred quantity, delivery date, a comment, and the product configuration. The submission is emailed to the store and added to a list in the panel.
- This is a sales inquiry - it doesn't create an offer or a quote in the store; further contact is handled by store staff. A price request with a history in the store is handled by Quotes.
- Customer offers and the "Ask for an offer" form - features older than version 2.28.
- Last changes to the module: version 2.35.0.
- The BS5 or BS4 store template - both have offer views.
- A customer account - only a logged-in customer creates offers.
- The offer's PDF document template, among the message templates (prepared during implementation).
- Viewing employees' offers - company accounts (Company accounts and roles).
- The "Ask for an offer" form - a button on the product page and an email address the submissions go to; in its current form it's tied to the product configurator.
- Requires implementation - the module doesn't turn on by itself after an update. Scope:
- turning on the module and choosing the store views the offers apply to,
- choosing how the price is calculated (discount, margin, markup),
- the offer's PDF document with the store's data and look, optionally Excel,
- offer view labels in the store's languages,
- "Ask for an offer": a button on the product page, marking products, the form, and the email template,
- translating messages, if the store runs in languages other than Polish,
- testing in a test environment and going live.
- Minimum estimated time:
- customer offers - BS5 and BS4 templates from 6 h,
- the "Ask for an offer" form - from 4 h.
- The time for a specific implementation depends on its scope - we quote it individually.
- What the time depends on:
- how much the offer document and the customer account views are customized,
- the link to company accounts,
- the number of languages,
- additional requirements, e.g. passing offers to the ERP (quoted separately).
- The customer creates the offer for their own buyer - the store doesn't prepare offers for the customer in the panel.
- The store doesn't send the offer to the buyer and doesn't collect their decision - the customer hands over the document themselves, outside the store.
- The offer has no statuses or a validity period; after adding to the cart, products come back at the store's current prices; items outside the catalog aren't supported; offers aren't created from a quote; there's no list of offers in the panel.
- In the standard configuration the price changes by a discount for the whole offer; margin and markup need a change during implementation, and separate prices per line item need custom work.
- The offer's PDF template has to be prepared during implementation - the module doesn't ship a ready-made design.
- The "Ask for an offer" form is an email submission - it doesn't create an offer or a quote and is tied to the product configurator.
- REST API and MCP don't support offers - passing them to the ERP requires a separate integration.
- We do not verify the configuration for legal compliance - the content of offers and the commercial terms between the reseller and their buyers are set by the store and its customers.
- Offer statuses (Draft, Ready, Sent, Accepted, Rejected, Expired) with a validity period and automatic expiry.
- Offer line items also from the product page, from a ready or accepted quote, or outside the catalog (name, description, unit, price, VAT, discount, photo).
- Setting the price by discount, margin, or markup also separately for individual offer line items, recalculated live.
- An offer added to the cart keeps the offer's prices through to the order.
- Attachments to the offer and saving successive versions of generated documents.
- A "Priced products" list in the customer account, searchable by product, quote number, and offer number.
- Offers prepared by the store's sales rep for the customer, in the panel (viewing, editing, and changing the status of customers' offers).
- Emailing the offer to the buyer with acceptance or rejection by link, plus notifications about status changes and approaching expiry.
- Offer documents in Word format with the store's or the customer's template.
- Offer support in REST API and MCP, and passing offers to the ERP.
Can only business customers prepare offers?
The offer is created by a logged-in customer for their own buyer - typically a B2B reseller (installer, distributor), but the feature isn't limited to company accounts.
Does the store send the offer to the customer's buyer?
No. The customer generates the PDF (or Excel) document themselves and hands it to the buyer outside the store.
Can the price in the offer be calculated by margin or markup, not only discount?
Yes. Calculating by margin or markup is available in the module and requires enabling during implementation; by default the price changes by a discount for the whole offer.
Do products from a saved offer come back to the cart at the offer's prices?
No. Products from the offer go into the cart at the store's current prices, not the prices saved in the offer.
How long does implementing offers and the "Ask for an offer" form take?
Customer offers in the BS5 and BS4 templates - from 6 h, the "Ask for an offer" form - from 4 h. The exact time depends on the implementation scope.
Are offers available in REST API or through the AI assistant (MCP)?
No. REST API and MCP currently don't support offers.
Want to see how offers could work in your store? Contact the Hummerce team (in Polish).
- Customer account: "List of prepared offers", for the company manager - "Company offers".
- Quote requests in the panel: "Ask for an offer" forms.
- Panel configuration: the Offers group - Module is available, Default offer limit in the customer panel (10 by default).
- Customer: the "Offer symbol format" parameter.
¶ REST API and MCP
Messages are changed in the message editor, document and email templates - in email templates, properties and locations - in Properties and locations.
| Key |
Default value |
msg.profileMenu.offerList |
List of prepared offers |
msg.profileMenu.offerList.description |
List of prepared offers |
msg.offer.generatePdf, generateExcel |
Generate pdf, Generate excel |
msg.form.askForOffert, msg.form.askForOffert.title |
Ask for an offer |
msg.form.askForOffert.tooltip |
To ask for an offer, configure the product |
mailform.askForOffer._firstName, _lastName, _email, _phone |
First name, Last name, E-mail, Phone |
mailform.askForOffer._preferredQuantity, _delivery_date, _comment |
Preferred quantity, Delivery date, Message |
Offer view labels (e.g. dates, buyer data, net prices and totals, saving and deleting the offer) are adjusted in the message editor during implementation.
| Symbol |
Object |
Label |
_customerOfferTemplate |
customer |
Offer symbol format |
_offerDiscount |
offer |
Discount |
_customerOfferMargin |
offer |
Margin |
_offerTransportPrice |
offer |
Transport cost |
_offerMontagePrice |
offer |
Assembly cost |
Property locations: offerCustomerData (offer - buyer data), cartItemShopCopyToOffer (cart item - properties copied to the offer), offerItemShopCopyToCartItem (offer item - properties copied to the cart item).
Email templates: newOfferForCustomerAsPdf - the offer's PDF document template (not sent by email), askForOfferMail - to store staff, on a new "Ask for an offer" submission.