GoSeedly Catering Kit / INSTALLATION
Bring the kit into your compatible Seedly installation, preserve existing work, and choose the starter content that fits your team.
Use your separately obtained Seedly CRM 5.8.4 installation with extension API 1, a configured backend, and working authentication. Keep a private source checkpoint, including existing customizations. Use Node.js 20 or newer.
Extract the kit outside the Seedly source folder. From the kit directory, run node setup.mjs. The check identifies supported integration files, changed files, and destination conflicts before installation.
Deploy the included required helper from your authoritative backend source before connected edits. Follow QUICKSTART.md with your project’s existing package manager. Build the web app, sign in, and open your existing /location/YOUR_LOCATION_ID address. Verify access, navigation, and your important CRM flows.
Frontend installation and optional account content are separate. The included original catering helper is required for connected creation, editing and starter setup. It preserves native account permissions and unrelated custom fields, re-checks the quote line arithmetic and the quote record rules, and compares the current record state before saving. It exposes no stage mutation at all, so pipeline stages stay in your CRM’s own views under your existing roles. Deploy the helper from your authoritative backend source before connected edits. Pipeline presets and workflow drafts remain optional. Follow QUICKSTART.md and STARTER_CONTENT.md for the exact integration. The frontend installer does not deploy your backend.
Starter setup offers Event inquiries and quotes, Confirmed events, Corporate accounts, Tastings and menu development. Select individual pipelines and drafts, or use a suitable existing pipeline with the exact stage needed by the chosen draft.
All nine workflows remain inactive drafts. Review their native triggers, internal tasks, notes, timing, and assignments before publishing in Seedly. Timed waits do not check whether a task is complete or the stage has changed. These examples do not send customer messages.
Explore nine fictional events spread across the eight stages of the sample pipeline, from a wedding dinner already accepted to a gala being re-quoted and a wedding lunch that was declined, each with its menu lines, staffing counts and prep tasks. Example edits stay in the current page’s memory and reset on navigation or reload; sample events are never inserted into your CRM. Add ?example=1 to the home or custom-view URL. Leave sample mode to return to your real account.
INSTALLING WITH AN AI AGENT?
Existing records and unrelated custom source do not require starting over. Modified integration files need a deliberate merge.
Edit apps/web/components/devlaunch-catering/config.ts to set company name, descriptor, and default pipeline name, then rebuild. The design applies to the entire web installation. Use separate web installations to evaluate different full-interface kits, rather than stacking their installers.
Review unused starter additions for removal in Starter setup before removing the frontend. Server checks preserve edited or published workflows and pipelines with jobs or references. The process targets recorded kit additions rather than sweeping account records.
Preserve your local configuration and source edits. Preview frontend removal with node setup.mjs remove "/path/to/seedly" --dry-run. The automatic uninstaller uses a private restoration receipt and refuses to overwrite later edits. Keep that receipt private and out of public hosting or source exports. Removing frontend files does not remove account data or undeploy backend functions.
For an update, follow the documented removal/install process and reapply your preserved changes. A manually merged installation needs its own private change ledger and reviewed source rollback.
An event is a native contact-linked opportunity with a namespaced event type, recorded date and service time, venue label, service style, headcount, dietary notes, quote record, next-step note, menu lines, staffing rows and prep tasks. The recorded quote reference stays separate from native opportunity value. Other custom fields are preserved.
Every number is a reference somebody entered, or arithmetic on what somebody entered. Nothing is invoiced, deposited, collected, signed or recognized as revenue. There is no inventory, purchasing, recipe costing or food cost percentage. Staffing rows are role labels, counts and call times that roster nobody and touch no payroll. Event dates, service times and call times reserve nothing and create no calendar entry. Nothing in the kit messages a client, a venue or a staff member. Totals are grouped by currency and never added across currencies. The pipeline stage stays your CRM’s own: the kit adds no stage model and no stage mutation, and the recorded quote status is a separate field.
The kit’s original operational screens share the frame with full CRM modules from your own Seedly source. Existing account permissions, feature gates, and configured providers still determine access to those modules.
See the interface and everything included.
Back to GoSeedly Catering KitWe use essential storage to keep the site working. With your permission, we also use analytics and the Whop Pixel to understand visits and advertising results. Optional analytics stay off until you choose.
Read our Cookie Policy and Privacy Policy.