Importifier
Features

What Importifier actually does.

No bullet-point soup. Each section below explains what the feature is, how it works, and the specific operator pain it takes off your plate. Skip to whatever's most relevant.

01 · Online ordering

Take orders 24/7. Get paid faster. Stop chasing PDFs.

The single biggest gap in the existing distributor software landscape (specifically: ChannelSnap, the incumbent for Ontario boutique importers) is the inability to actually take payment. They generate an invoice; you forward it to your customer; the customer pays by e-transfer or cheque or forgets entirely. You spend the back end of every month reconciling.

Importifier ships card payments out of the box. Your customer hits your storefront, builds a cart from your public-visible SKUs, picks "Pay by card" or "Send me an invoice," and either pays Converge directly (funds settle to your bank) or generates a draft invoice for your review. If they want an invoice, you see it on your dashboard tagged "needs review" — apply the right pricing tier, send it out, done.

Tier pricing is automatic. A licensee gets their wholesale price; a private client gets retail. The difference shows up at the line-item level, on the invoice PDF, and in your reports. The "Apply [tier] pricing" button on draft orders lets you re-price an order at the customer's tier in one click if they switch.

Specifics
  • · Card payments via Converge (Elavon Canada) — Canadian processor, $CAD settlements
  • · Invoice request flow with operator review before send
  • · Per-customer tier pricing (wholesale, retail, custom) applied at line level
  • · Order acknowledgment emails to customer on payment / invoice send
  • · Public payment links — your customer pays without logging in
  • · Card-on-file tokenization for repeat customers (no PCI scope on your end)
  • · Sandbox mode in staging means you can practice without real charges
02 · LCBO automation

Less re-keying. Less stress at month-end.

Boutique agents on the LCBO's elite (Specialty Services) system live in three xlsx files: a master portfolio they maintain, three daily reports the LCBO emails them, and per-PO emails from [email protected] that need to land in inventory. ChannelSnap helps with the portfolio submission but requires manual upload of the daily reports. Everything else is by hand.

Importifier's portfolio submission generates the canonical xlsx the LCBO expects — SCC code, vintage, pack, container size, supplier, port, the whole hierarchy — from your catalog. No more side-by-side spreadsheet wrangling to reformat what you already have in your own system.

Daily report ingestion runs on a schedule. Stock on Hand Master updates SKU-level inventory. POs in Transit and POs in 'A' Status update purchase order state. You stop opening the daily LCBO email and start trusting your dashboard reflects the real LCBO position.

Specifics
  • · Portfolio xlsx export in the LCBO's expected schema
  • · Daily ingestion of Stock on Hand Master, POs in Transit, POs in 'A' Status
  • · LCBO supplier numbers, port numbers, PO numbers, SCC codes carried as first-class fields
  • · Inventory deltas surface as alerts on the dashboard
  • · Per-PO email parsing (auto-import of PO data from [email protected]) on the roadmap
03 · Storefront

Your online presence, your way.

Two paths, depending on whether you have an existing website you love:

Use our hosted templates. Pick from four presets — classic, editorial, minimal, cellar — each tuned for the wine-magazine aesthetic rather than the generic e-commerce template look. Set a hero image, brand color, tagline, and featured products, and you're shippable. Brand-new tenants are typically live in under an hour.

Keep your existing site. If you've already invested in a Squarespace / Wix / custom site you don't want to abandon, embed our shopping cart as a JavaScript component on your existing pages. Your pretty design stays; customers get a real ordering flow. (This path is on the immediate roadmap — first beta customer is on hosted templates.)

Custom domain support is built in. Bring your own myimports.com, point DNS at us, and we provision a free Let's Encrypt certificate automatically. We don't add a parked .importifier.com subdomain — the domain that serves your storefront is your domain.

Specifics
  • · Four landing-page templates (classic, editorial, minimal, cellar)
  • · URL importer — paste your existing site URL, we pre-fill landing fields from meta tags + JSON-LD
  • · Brand color, hero image, tagline, intro paragraph, contact email — all editable inline
  • · Featured-products picker (curate which SKUs appear on the landing)
  • · Public + private SKU visibility flag (control what customers see)
  • · Cart, checkout, order confirmation pages all themed to match
  • · Custom domain attachment with auto-provisioned Let's Encrypt cert
  • · Embeddable cart component (roadmap)
04 · Catalog & operations

The boring foundation, done right.

Every distributor needs the same primitives: producers, products, suppliers, inventory, customers, orders, invoices, and the audit trail your accountant assumes exists. Importifier has each one as a first-class entity, not a row in a spreadsheet you maintain on the side.

Wine and spirits live in the same schema with discriminator fields, so a wine-only tenant doesn't see spirits-specific forms and vice versa. Single codebase, but the operator experience is tuned per category.

Customer tiers are explicit. Every customer is tagged with a tier (wholesale / private / restaurant / etc.); pricing applies automatically based on the tier. Orders carry their pricing tier as a snapshot, so historical orders reflect the price the customer actually paid even if the tier definition changes later.

Audit logging is coarse but coherent. Every meaningful write — order created, invoice sent, inventory adjusted, customer pricing tier changed — generates an audit row with actor, action, target, and a structured payload. The audit log is searchable by tenant operator and exportable in full.

What's modeled
  • · Producers — wineries / distilleries you represent (country, region, type, notes)
  • · Products — SKU-level catalog (vintage, container size, alcohol %, image, description, public/private flag)
  • · Suppliers — your importer / wholesaler partners; many-to-many with producers
  • · Inventory — per-SKU stock levels, case counts, LCBO stock tie-in
  • · Customers — licensees with tier-based pricing, contact info, payment method on file, order history
  • · Orders — draft → confirmed → fulfilled, with per-line pricing snapshots
  • · Invoices — generated from orders, with public payment links + email delivery
  • · Deliveries — calendar view of scheduled deliveries by customer
  • · Reports — revenue, inventory turn, customer activity (more coming)
  • · Audit log — every write logged with actor, action, target, payload
05 · Data sovereignty

Your data is yours. Provably.

The market for distributor SaaS is dominated by US-hosted products with vague data terms. We took a different position: hosted in Canada, multi-cloud, isolated at the database layer, and exportable any time without asking permission.

Primary infrastructure runs on DigitalOcean Toronto. Backups go to Google Cloud Storage in Toronto, encrypted with a Cloud KMS key wrapped by an offline age envelope key we control. The trust boundary between primary and backup is deliberate — a compromised cloud provider can't see your backup keys.

Tenant isolation isn't just an application-layer WHERE tenant_id = ?. We use Postgres row-level security (RLS), which Postgres enforces regardless of what our application code does. A bug in our code can't leak another tenant's data, period — RLS catches it at the database layer.

Disaster recovery is tested quarterly by restoring the latest backup into a standing GCP project (Cloud Run + Cloud SQL) and running smoke tests against it. Restored tenant data, restored pricing, restored audit logs.

Specifics
  • · Primary: DigitalOcean Toronto (TOR1 region) — App Platform + managed Postgres
  • · Backups: Google Cloud Storage Toronto, daily, KMS-encrypted with an offline age envelope key
  • · DR target: standing GCP project (Cloud Run + Cloud SQL), restored quarterly
  • · Postgres RLS on every tenant-scoped table
  • · Full data export on demand: catalog, customers, orders, invoices, audit log — your format, no friction
  • · No vendor lock-in clause anywhere in our terms of service
  • · Audit log retention is your choice — we don't auto-prune
06 · On the roadmap

What's coming next.

Importifier is in private beta and we're building toward feature parity (and beyond) with the incumbent distributor tools. Beta customers get the full roadmap with delivery estimates. Short version of what's in flight:

  • · LCBO PO email parsing — auto-import POs from [email protected] without operator action
  • · Embeddable cart component — drop-in JS for tenants on Squarespace / Wix / custom sites
  • · Spirits extension — full distillery-side workflow alongside the wine flow
  • · Per-tenant custom domains — tenant operator self-serves the domain attachment via the editor
  • · Quickbooks integration — push invoices to QBO directly
  • · Mobile-friendlier operator views — current operator UI is desktop-first

Ready to see this on your portfolio?

We'll set up a tenant with your actual products loaded — no synthetic demo data — so the demo is the real thing.

Request access