Skip to content
View packages

CRM KitsGift shops and boutiques

Ready on its day. Every order.

A gift shop lives on the order somebody paid a deposit on three weeks ago. Ribbon puts a fourteen day pickup strip on a white canvas under a zinc charcoal bar, with a turquoise ready state and a gift wrap flag drawn right on the card.

Pickup strip in the GoSeedly Gift Shop Kit with fictional sample records

Fourteen days, side by side.

Each day column holds the orders due for pickup that day as compact cards, with the customer label, the item count, a gift wrap flag and the readiness word. The corporate accounts row sits underneath, and a past due strip appears when an order has slipped.

Actual interface captures with fictional sample data. Open a screenshot to see it full size.

What’s in the kit

Screens

  • Fourteen day pickup strip with a corporate accounts row, past due and undated strips
  • Order sheet with item rows and corporate recipient rows
  • All orders table by recorded pickup date with the native stage control
  • Corporate account and seasonal reorder groupings
  • Shop insights drawn from recorded workspace data
  • Zinc charcoal and turquoise Ribbon application frame with full CRM tools

four pipelines

  • Custom orders · 8 stages
  • Corporate gifting · 7 stages
  • Seasonal and holiday orders · 7 stages
  • Wholesale and consignment · 7 stages

Optional. Install the ones that match your work, or connect drafts to a pipeline you already use.

nine workflow drafts

  • Order confirmation note
  • Personalization check task
  • Item sourcing task
  • Ready for pickup task
  • Post-pickup thank-you task
  • Corporate recipient list task
  • Delivery confirmation note
  • Pickup reminder
  • Seasonal reorder reminder

Inactive until you review and publish them. None send customer messages.

Sample workspace

Explore sixteen fictional orders in the separate sample view, with thirty-three item rows and seventeen recipient rows across three corporate accounts. Fifteen sit inside the fourteen day window and one is past due. Example edits stay in the current page’s memory and reset on navigation or reload; sample orders are never inserted into your CRM.

No sample customers are added to your CRM.

Setup and source

  • Guided setup and compatibility report
  • Private rollback receipt
  • AI-agent guide for customized installations
  • Original editable source, configuration, and tests
Read the installation guide
  1. Check your Seedly

    Extract the kit and run the guided setup. It checks your installation and flags customized files before it changes anything.

  2. Connect the helper

    Deploy the included helper from your backend source, then build your web app and choose any starter pipelines and drafts.

  3. Make it yours

    Set shop name, descriptor, and default pipeline name. Then sign in and check the workflows and permissions your team uses.

Technical details and compatibility

Seedly CRM 5.8.4 · extension API 1. Node.js 20 or newer. The installer checks supported integration-file versions and does not deploy your web app or backend. The included original gift shop helper is required for connected creation, editing and starter setup. It preserves native account permissions and unrelated custom fields, re-checks every cross-field rule, and compares the current record timestamp and order revision before saving. Deploy it from your authoritative backend source before connected edits. Pipeline presets and workflow drafts remain optional.

One order is a native contact-linked opportunity with a namespaced order type, pickup date, gift wrap flag, message card text, readiness state, season label, corporate account label, last reorder date, an optional order total and notes, plus item rows and recipient rows with stable IDs. Other custom fields are preserved.

Readiness, the sourced flag and the delivered flag are staff-entered records. A recorded pickup date reserves nothing, creates no native Calendar appointment and sends no reminder; a date that has passed moves the order into a past due strip rather than hiding it. Seven cross-field rules are enforced on both the client and the server: a ready or picked up order needs a pickup date, a picked up order needs every item recorded sourced, a corporate order needs a corporate account, only a corporate order records recipients, a seasonal order needs a season label, a reorder date belongs to a seasonal order, and a recipient is only recorded delivered once the order is ready. The kit has no point of sale, inventory, product catalog, supplier ordering, shipping, payment processing, customer messaging or storefront.

Four optional pipeline templates and nine inactive workflow drafts. Sixteen fictional in-memory orders with thirty-three item rows and seventeen recipient rows.

Calling, messaging, signing, payments, and external integrations depend on your Seedly installation, account permissions, plan, and configured providers. Screenshots use sample data and reference imagery. Hosting, installation, and ongoing maintenance are your responsibility.

Get the Gift Shop Kit

Checking access…

DevLaunch All Access

Every kit and every template.

See DevLaunch All Access

Already a member? Open your downloads.

Questions

How do I receive the kit?

Purchase securely through Whop. Your original source ZIP and installation documentation are delivered manually to the email used at checkout. This is a one-time purchase of this kit; Seedly software, hosting, and installation services are separate.

Does this include Seedly CRM?

You obtain and configure Seedly separately. The kit adds original frontend screens, a shared theme, starter definitions, and integration instructions. It does not include Seedly’s codebase, license, hosting, or a separate CRM database.

Is this one connected workspace?

Ribbon keeps its single chrome bar across the original gift shop views and the native CRM modules. Full CRM tools remain available within the same signed-in account and application theme. Contacts, Calendar, Estimates, Documents, and other full modules retain the functionality supplied by your own Seedly installation. Existing authored content and provider screens retain their own layouts.

Can I use it with existing customizations?

Yes, with a compatibility review. The installer checks the supported integration files. Changed integration files need a reviewed merge; the included AI-agent guide explains how to preserve custom extensions, permissions, providers, and routes.

Do I have to import all the starter content?

No. Choose individual pipelines and workflow drafts, use a compatible existing pipeline, or install none. Workflows remain inactive until reviewed and published. They use native triggers, internal tasks, optional notes, and timed waits. A wait does not verify task completion or recheck the current stage. The included drafts do not send customer messages.

Can I remove the examples and starter content?

Sample records stay in memory and never create customers in your CRM. Leave sample mode to return to your account. Starter setup lets you review removal of unused kit additions; server checks retain edited or published workflows and pipelines with live work or references. Removing the frontend does not delete account records.

Can different subaccounts use different kits?

The current design and branding apply to the whole web installation. Subaccounts still separate data and access. Use a separate web installation for another full-interface kit; running different kit designs by subaccount in one installation requires additional customization.

Browse all 220 kits

Customer experiences / Trustpilot

What customers say
about DevLaunch.

Read all reviews on Trustpilot ↗

Selected excerpts from reviews of DevLaunch training, software, and services. Individual customer experiences across DevLaunch.