Home

904Barndo

HomePlansCustomGalleryProcessAbout
904Barndo

Explore

PlansCustom BuildGalleryProcessAboutMy Plans

Trust

TermsPlan LicensePrivacyRefunds & Disputes

Stripe checkout

MFA accounts

Florida-focused

© 2026 904Barndo LLC

Jacksonville, FL904-9-BARNDOMail@904barndo.com

Owner Workflow

A no-code publishing flow for plans, gallery updates, files, and promos.

Use the admin panel to add a plan, upload media, attach protected files, adjust pricing, and publish new plan or Gallery URLs without editing the codebase.

View StorefrontView Gallery

Auto-generated plan slugs

Gallery latest + archive flow

CMS-managed prices and descriptions

Publishing Flow

The order of operations is simple on purpose.

Once the upload and plan records exist in Payload, the storefront and checkout use them directly.

1. Add media first

In the admin panel, upload storefront and editorial images in Media Library. The first gallery image becomes the card/hero image the storefront uses.

2. Upload protected files

Upload PDFs, CAD files, and material lists in Protected Deliverables. Those files stay behind the buyer account download route and can live in private object storage.

3. Create or update the plan

Open Plans, fill in the overview, pricing, packages, and add-ons, then attach the uploaded media and deliverables. The slug auto-builds from the plan name for the public URL.

4. Publish and promote

Set the plan or Gallery update status to Published when it is ready. Optional public sales and private offers can be created in Promotions without editing code.

Guardrails

The admin protects the parts that should not drift.

A sold plan should stay stable for buyers who already purchased it, so the workflow favors safe updates over destructive edits.

Published plans and price changes appear on the live storefront without a rebuild.
The newest published Gallery update is featured automatically, while older published entries move into the archive section below it.
The first gallery image becomes the storefront card image, so keep it polished.
Sold plan slugs, sold package IDs, and referenced deliverables are guarded so history does not break.
If a deliverable needs a new version, upload a new protected asset and remap the plan instead of replacing the sold file in place.