Write a newsletter, choose who gets it, and send — to the customer groups already in your address book, with no export, no upload and no second subscriber list to keep in step.

The list you already have

Most wine businesses run their mailings from a copy of their customer list, exported once and slowly diverging from the real one ever since. Somebody unsubscribes in the mailing tool and keeps receiving invoices addressed to a name they asked you to drop; somebody changes address in the CRM and the newsletter still goes to the old one.

Vinosoft removes the copy. Recipients are your addresses, groups are your groups, and an unsubscribe is recorded on the customer record itself — so the person who opted out is opted out everywhere, and the list is as current as the last order you entered.

Building the mailing

Recipient groups you define — a wine club, restaurant customers, a region, subscribers to a single range
A drag-and-drop template editor (BEE) for reusable layouts that match your labels and your website
Merge tags for personalisation, so the salutation is the customer's own
A test send to yourself before the template is saved, because a broken layout is not fixable after the fact
Your own sender address, so replies come back to a mailbox you read

Sending, and knowing what happened

A send goes through the email queue rather than out of a browser tab. Start it, and you can watch it work: how many messages were sent, how many were flagged, how many failed, and the message body as any individual recipient received it. If a large send has to happen while the office is closed, it runs without anyone watching it.

The email log covers everything else Vinosoft sends — invoices, order confirmations, quotes, dunning letters — with recipient, subject, date and delivery status, so "we never got it" is a question with an answer.

Where the addresses come from

Subscribers are added by hand, imported from a file, or already present as customers. Group membership is what a send targets, and a customer can sit in several groups at once. See Address management for how those records and groups are maintained.

Consent that stays where it belongs

A subscription is a state on the customer record: subscribed, unsubscribed, and when. Opt-ins collected at the web shop's checkout land on the same record, and an unsubscribe from any mailing applies to all of them. There is no second list to reconcile, and no way to mail somebody who asked you not to because a stale export said otherwise.

Read the documentation

Create and send a newsletter — composing, addressing and sending
Manage recipient groups — who receives what
Manage newsletter recipients — adding, importing and subscription status
Design templates with the BEE editor — reusable layouts and merge tags
Monitor the email queue — tracking a send in progress