Farm Post Office · Invitation prototype 001
A small invitation to a working experiment

Let your farm's systems talk to each other.

Orders, memberships, and email lists shouldn't require copying names from one place to another. We're building a farmer-controlled bridge between the tools you already use.

No account · No real customer data · Nothing connected during this demo

The idea

Connect systems. Keep control.

We aren't asking you to replace your storefront or email provider. The goal is automatic, permission-aware communication between them, even when they belong to different organizations.

Your existing store

Something happens

A customer places an order or joins a CSA. Your data stays under your control.

reLATTE

The post office

Records where the notice came from, asks what is permitted, and keeps a receipt.

Your email tool

The appropriate action

Update a contact, apply an unsubscribe, or send only when your rules allow it.

Important distinction: Buying vegetables does not automatically subscribe someone to marketing emails. The bridge has to respect opt-ins, unsubscribes, and the farmer's own rules.
Hands-on sandbox

Try sending an imaginary change.

Click an event and watch what a farmer's operator panel could report. Everything below is simulated in this browser using fictional records. It does not connect to real farm software or send emails.

Choose a sample event

The real reLATTE library provides signed crossings, local decisions, and retry primitives. This page demonstrates their intended operator experience, not a live connection.

The farm mailroom

Simulation only

Storefront → permissions → email service

0Applied
0Held
0Delayed

No sample events yet. Choose one on the left.

No real customers, messages, credentials, or live integrations are used here.
First farm pilot

Start with one small useful connection.

Our first proposed trial is simple: one authorized storefront change automatically updates one appropriate record in your chosen email system, with a receipt you can inspect. Start with synthetic data or a few agreed-upon test records, not your entire customer list.

What we'd work out together

Which storefront are you using?

For example, a co-op e-commerce service, a farm shop, or a CSA platform.

What handles your emails?

Could be a newsletter provider, a CRM, or email marketing inside your website.

What would help first?

New contacts, CSA segments, fulfillment notices, or preventing unsubscribed people from receiving mail.

Who approves the connection?

You choose the rules and grant access only if you decide to proceed. No password sharing.

Experimental prototype · No cost or commitment to explore fit · Scope, any ongoing costs, and responsibilities would be agreed before real integration.

Make your own pilot note

These answers stay on this page until you choose to copy them. Nothing here is sent to us.

Safe first stepPlease don't enter customer information, passwords, API keys, or private records. A real connection would use an agreed authorization method and a separate private setup.

Copy the note and reply to the person who invited you. The email draft intentionally leaves the recipient blank; you choose whom to send it to.

Curious, but not ready to connect anything?

That's fine. The first conversation can be a ten-minute screen share about which tools you already use and where information gets stuck. We can show an automated sample with no access to your systems.