Documentation/Sharing
White-label
On the Enterprise plan: the shop's customers see no MetronQ name, under the shop's own domain and mail server.
Availability
White-label is part of the Enterprise plan. MetronQ switches it on for an account after the terms are agreed with the shop; the plan alone does not include it. It stops working when the account leaves the Enterprise plan, and while MetronQ has suspended the widget configuration. When it is on, the Widget tab, “Design” view, shows “White-label is on”.
What the customer no longer sees
- The widget and the hosted page have no MetronQ footer. The browser tab shows the shop's name, with the shop's logo as its icon, or a tile with the first letter of the name when there is no logo.
- The default note on personal data in the order form names the shop and “the software and hosting providers it uses”, without MetronQ's name. A note the shop wrote in “Texts” is shown as written.
- The quote PDF has no line naming MetronQ, and the shop's name is the document's author.
- Customer e-mails carry the shop's name at the top in place of MetronQ's logo, no MetronQ address, link or social profile in the footer, and the shop's name as the sender's name.
For every shop, with or without white-label: a customer e-mail is answered to the shop's contact address (Reply-To, the address the account was registered with), and its footer says it was sent for the shop. To change the contact address, write to MetronQ.
The shop's own domain
The widget, the hosted page and the links in customer e-mails can run under a subdomain of the shop's own domain, for example quotes.yourshop.com. The shop owns the name; MetronQ buys no domain and changes no DNS record. The section “Your own domain” is in Settings, tab Company, and is available to the owner.
- 1Enter the subdomain in “Domain”, without https:// and without a path. An address of MetronQ, or a domain another account uses, is refused.
- 2At the domain registrar, add the CNAME record the section shows: the name points at quoting.metronq.com. It must be the only record for that name, with no proxy in front of it (in Cloudflare: “DNS only”).
- 3Select “Write to us”. MetronQ checks the record and approves the name, and the server issues its certificate. The section shows “Approved” and, within a few minutes, “Active. Your quote page:” with the address.
- Under an active domain the hosted page is the domain itself, with no shop name in the path. Quote links have the form https://quotes.yourshop.com/quote/1001, combined quote links /offer/1001.
- The Widget tab shows an embed code that loads the script from the shop's domain (/embed.js, attribute data-quote-key). A widget embedded with the earlier code keeps working from MetronQ's address.
- “Remove the domain”, or the end of white-label, sends the hosted page and the links in new e-mails back to the MetronQ address at once. Links already sent under the domain stop working.
- When the record does not point at MetronQ's server, the section says so and the name waits. After the record is corrected, write to MetronQ again.
The shop's own mail server
Settings, tab Notifications, section “Mail to your customers”, available to the owner. With a server set and switched on, the seven messages a customer receives leave from the shop's address through the shop's server: quote ready, updated quote, order received, order confirmed, order shipped, combined quote, order from a combined quote. Every other message MetronQ sends leaves from MetronQ's servers as before. Fields:
- “Server”: the server's name, for example smtp.example.com. An IP address is refused: the server's certificate is checked against the name.
- “Port”: 587 (STARTTLS) or 465 (TLS). The connection is always encrypted and the certificate is verified.
- “Login” and “Password”. The password is stored encrypted and never shown again; with one stored, the field reads “Stored. Leave empty to keep it.”
- “Sender address”: the address customers see. The server has to be allowed to send from it.
- “Sender name”: shown beside the address. Empty: the shop's name.
- 1Fill in the fields and select “Save”.
- 2Select “Send a test message”. A message goes through the server to the signed-in owner's own address, at most 6 tests an hour. The result is shown in the section.
- 3After a test went through, tick “Send messages to my customers through this server”.
- A change to the server, port, login, password or sender address switches the server off until a new test goes through.
- A message the server refuses is not sent from MetronQ's domain instead. It is marked as failed, the section shows “The last message to a customer was not sent:” with the reason, and the bell shows “A message to your customer was not sent”.
- Bounces go to the shop's mailbox. The panel does not show them.
- Without a server switched on, customer messages leave from MetronQ's mailbox under the shop's name.
- “Remove the server” deletes the settings.
Wording of customer messages
Section “Wording of customer messages”, under the mail server. The table lists the seven messages with “Sent” (when the message goes out) and “Wording” (“Standard”, or “Own:” with the languages written). “Edit” opens one message:
- One tab for each language the shop offers. The fields start from MetronQ's text in that language.
- “Subject”: one line, up to 200 characters. “Text”: up to 4000 characters. An empty line starts a new paragraph, and two asterisks on each side make text bold. Links and HTML are shown as typed.
- “Fields”: the message's placeholders. A click puts one at the cursor, and each is replaced with its value when the message is sent. A placeholder the message does not have is refused.
- A message that gives the access code keeps {access_code} in the text. The code cannot go into the subject.
- The button, the details table and the footer are added by MetronQ and cannot be changed.
- “Preview” shows the message as the customer receives it, with sample data. “Restore the standard text” deletes the shop's text for that message and language.
Placeholders: “Quote ready” and “Updated quote”: {shop}, {access_code}. “Order received”: {shop}, {name}, {access_code}. “Order confirmed”: {shop}, {name}, {filename}, {quantity}, {total}, {currency}. “Order shipped”: {shop}, {name}, {filename}, {quantity}. “Combined quote”: {shop}, {access_code}, {count}. “Order from a combined quote”: {shop}, {name}, {access_code}. Every message also has {support_email}, the shop's contact address.
The shop's wording is sent only through the shop's own mail server. Without one switched on, the section says so and customers receive the standard text. A language the shop did not write gets MetronQ's text in that language.
Colour and logo in e-mails
- The header and the button of a customer e-mail take the accent colour published in the Design view, with white or black text, whichever reads better on it. Without a colour: navy.
- The logo appears in the header when the account has an active own domain and a logo uploaded in the Design view. The e-mail client loads it from the shop's domain as a PNG. Otherwise the header shows the shop's name.
The API for the shop's own pages
A shop that shows its customers pages of its own instead of the widget reads and orders through the integration API: the customer view of a quote, the quantity table, placing an order (permission orders:create) and the flat DXF of a bent part. Verdicts on quotes from the shop's own system (permission quotes:review) are switched on by MetronQ by agreement, like white-label.
What a developer can still see
White-label covers what the customer sees on the pages, in documents and in e-mails. The browser's developer tools still show:
- the X-Metronq-Key header of the widget's requests;
- the address of the storage service the file is uploaded to;
- the names of the messages between the widget and the page that embeds it (metronq:...) and the widget's CSS classes (mq-...);
- MetronQ's addresses for the script and the API when the widget is embedded with the code that loads it from MetronQ.