Seeed

About Seeed

Seeed is a Miami-based custom software agency founded in 2014. Our team of 30 engineers, project managers, and QA specialists builds production-grade Medusa.js storefronts for mid-market brands — from greenfield commerce builds to migrations off Shopify and WooCommerce. We specialize in the integrations that make Medusa work at scale: Square POS, ERP systems, PIMs, and custom backend logic. We're the most awarded Square developer partner globally — 4 hackathon wins over 3 consecutive years — which means the Square × Medusa integration layer other agencies scope as a risk, we've shipped in production. Our stack pairs Medusa with Next.js, Builder.io, Payload CMS, Strapi, Directus, or any other CMS deployed on Vercel or Google Cloud with SSR by default. Every storefront we build is AI-crawlable and search-indexable from day one. Enterprise-grade delivery without the enterprise price tag.

Medusa Cases

Seeed builds production-grade Medusa.js storefronts for mid-market brands — connecting Medusa's open-source commerce backend to the systems businesses actually run on: ERPs, PIMs, Square POS, and custom integrations. Every storefront ships on Next.js with SSR, so product catalogs are indexable, fast, and built to scale

Highlighted Case: Province Electric Supply — Magento Migration + DDI ERP Integration

Province Electric Supply ran their commerce on Magento and their operations on DDI by Advantive. The two systems didn't talk. Product data lived in DDI but had to be manually maintained in Magento — a double-entry problem that grew worse with every new SKU. Seeed migrated Province off Magento onto a Medusa.js storefront with a direct DDI integration layer and a centralized PIM. Product data, pricing, and inventory now flow from a single source of truth: DDI feeds the PIM, the PIM feeds Medusa, and the storefront reflects it automatically. Stock levels and order data sync back to DDI without manual reconciliation. Province's team can now update complex product attributes — specs, certifications, cross-references — without touching the storefront directly or maintaining parallel records across systems.

Seeed.us handled the full migration from Magento and built the DDI integration we'd been putting off for years. Our catalog is now managed in one place and the storefront stays in sync automatically — no manual work between systems.

Shawn Mole

·

CEO, Province Electric Supply

Other Medusa Cases

• Square × Medusa Plugin: Built a production-grade Medusa plugin connecting Square Payments and Square POS to Medusa — covering OAuth, bidirectional catalog sync, real-time inventory updates, and multi-location support. Actively maintained by Seeed's engineering team.
• Builder.io × Medusa Plugin: Developed Copy to clipboard@weareseeed/medusa-plugin-builder — the official connector between Medusa's Commerce API and Builder.io's visual CMS. Registers native Medusa product, collection, and category input types for any Builder component, with full SSR support.

Medusa Specializations

At Seeed, we build Medusa implementations for mid-market businesses that need more than a storefront — they need commerce connected to the systems running their operations. Our team has shipped custom Medusa plugins published on npm, direct ERP integrations, PIM connectors, and Square POS synchronization across live production environments.

Plugins & Starters

Seeed has published open-source plugins that extend Medusa's core for real production use cases:

• Copy to clipboard@weareseeed/medusa-plugin-builder — Connects Medusa's Commerce API to Builder.io's visual CMS. Adds native MedusaProduct, MedusaCollection, and MedusaCategory input types to any Builder component, with SSR auto-resolution so content renders server-side. Available on npm.
• @weareseeed/medusa-square-plugin — Bidirectional sync between Medusa and Square POS, covering OAuth, payments, catalog, real-time inventory, and multi-location support. Built and maintained by the most awarded Square developer partner globally.

What We're Best At

• Medusa migrations from Magento — data integrity, custom logic, ERP re-integration, zero-downtime cutover
• ERP connectivity — live integrations with DDI by Advantive, SAP, and custom ERP environments
• PIM integration — centralized product data pipelines feeding Medusa without manual reconciliation
• Square omnichannel — one integration covering online storefront, brick-and-mortar POS, and wholesale ordering, all synced through Medusa
• Headless storefronts on Next.js paired with the right CMS for the team — Builder.io, Payload CMS, Directus, Strapi, or Sanity — SSR by default, AI-crawlable, editable without developer involvement

Before Seeed writes a line of code, we map how the business actually runs — how products are sourced, how orders move from placement to fulfillment, where data gets stuck, and where people are doing manually what a system should handle. That operational understanding is what separates an integration that works from one that just connects. Every automation we build is designed around the real process, not a generic version of it.