🚧 Preview

Honest about where
we're at.

Farin is an early preview built from years of running a real bakery. It's powerful, but it's not perfect. This page is an honest breakdown of current limitations, what we're working on next, and how you can help shape what gets built.

⚠️
This is a preview release. There will be bugs. Please report them in the Feedback Hub inside the app — screenshots and steps to reproduce help a lot. We actively monitor it and prioritize fixes quickly.

🔒 Modules currently disabled

These exist in our internal system but aren't yet open — we need operator input to generalize them properly.

⚙️

Production Planning

Our production planning system is deeply tied to our specific label printers and QR-code workflow. The core logic is there, but the input/output pathways are too narrow to work well for other operations without becoming brittle. We expect we'll need 3–4 distinct implementation pathways depending on operation size and setup.

Want this? Email us or post in the Feedback Hub describing your current production workflow — how you batch, label, and track items. That context shapes what we build.

📦

Inventory Management

Inventory tracking is partially built, but we've paused it because every operation counts inventory differently — by weight, unit, batch, or location. Getting this wrong means bad data, which is worse than no data.

Want this? Tell us how your current inventory system works — what you track, how often you count, and what you need to know. Post in the Feedback Hub or email us directly.

💡
Feature requests are welcomed, not just tolerated. The platform was built in the context of one bakery. Things like timeclocks not tracking breaks aren't oversights — they're gaps we haven't needed ourselves yet. If you need it, it's likely an easy add. Just ask.

📤 Import & Export

We've built this over years without other systems in mind. Here's the situation and how to work with it.

Farin doesn't yet have many bulk import or export interfaces. That's a side-effect of being built as internal tooling — data went in by hand and stayed in. This changes as we open up to other operators.

The good news: the app is essentially a wrapper around a PostgreSQL database, so integrations are straightforward. Here's how to get your data in or out:

📥

Getting data in

Email us an example of data you need to bulk-load — recipes from Word docs, spreadsheets, your current system export. We'll help map and import it.

Examples: recipe libraries, customer lists, ingredient databases, historical orders.

📤

Getting data out

Tell us where you need to send data and the format required. Post in the Feedback Hub or email us with your destination system (e.g. QuickBooks Online) and any format spec.

Common needs: accounting exports, payroll reports, sales summaries.

🔑

For the technical

You can generate an API key in Settings and directly read or write your data via our fully documented REST endpoints. No waiting on us.

Scoped per-company, per-domain. Read-only or read-write depending on key permissions.

⚠️ Current limitations by module

Where the platform is narrower than it will eventually be.

💵

Payroll

Partial
  • Arizona only right now. Most states are straightforward to add — post in the Feedback Hub with the state (and city if it has a local income tax) and we'll prioritize it. Some states with highly complex filing requirements may take longer.
  • Tax filing is semi-manual. The system calculates all withholdings automatically and generates quarterly and annual forms ready to print, sign, and mail. You are responsible for submitting them. We provide full reports, payment amounts due, reminders, and instructions.
  • Direct deposit via Mercury Bank only. Mercury offers a full API, free for up to 100 payments/month ($29/mo for unlimited beyond that). Quick to set up. Stripe direct deposit can be enabled if needed at $1.50 per payment. Alternatively, pay via check, Zelle, or ACH through your own bank.
🧾

Accounting

Partial
  • Automatic transaction imports: Square and Stripe only. These are the two payment processors we use at the bakery. If you use a different processor, email or post in the Feedback Hub with the provider name and we'll look at adding an integration.
🛍️

Retail Ordering

Planned

We'd love to add consumer-facing retail ordering features, but we need to hear what operators actually need before building. Every operation is different.

Examples of things we're thinking about: product modifiers, weekly bread subscription orders, daily inventory caps for pre-orders, pickup windows, and loyalty. If any of these would help your business, tell us — and tell us how your current ordering flow works.

Your context shapes what gets built next.

The more we hear from operators with different setups, the faster we can generalize the platform. The Feedback Hub is the best place for bugs, feature requests, and workflow questions — or email us directly.

Free to start · No credit card required · Full platform access on day one