Store Pickup / Click & Collect (BOPIS) for Magento 2

Key Features

Dedicated store-pickup shipping method (custom carrier implementing CarrierInterface) shown natively in the Magento 2 checkout shipping step alongside existing methods

Google Maps store locator with branch search, distance sorting and map/list toggle, rendered as a Knockout/UiComponent in checkout and on a standalone locator page

Pickup date picker plus time-slot selection that only surfaces slots with remaining capacity, validated server-side before the quote is updated

Per-location slot capacity and concurrent-order limits enforced through a service-contract layer so two customers can't book the last slot

Opening hours, lunch breaks and per-store holiday/blackout calendars that automatically remove unavailable slots

Admin location manager: UiComponent grid + form (ACL-gated) for branches, addresses, geocoordinates, hours and capacity

Slot reservation persisted on the quote and transferred to the sales order via a quote-submit-before observer, with the chosen branch and time shown on order, invoice and emails

REST and GraphQL endpoints exposing locations and slot availability for PWA Studio / headless storefronts

Cron job that releases expired slot holds and keeps capacity accurate

Admin ACL resources so staff roles can be scoped to manage locations, view bookings or both

Order-grid column and filter for pickup branch so counter staff can pull their own pickups

Configurable as a Magento module under app/code/Ecosire/StorePickup with di.xml, system.xml config and full setup scripts — multi-store / website scoped

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your Magento 2.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

Store Pickup / Click & Collect (BOPIS) turns your physical locations into fulfillment points inside Magento 2. We register a dedicated store-pickup carrier (a custom Magento\Shipping\Model\Carrier\AbstractCarrier implementing CarrierInterface) that appears in the checkout shipping step, so collection sits alongside your existing flat-rate, table-rate or carrier methods — no fake address hacks.

When a shopper chooses pickup, a Google Maps store locator lets them pick a branch, then a date and time-slot selector offers only slots that still have capacity. Per-location opening hours, holidays and slot capacity are enforced server-side, so you never overbook a counter. Slot reservations are persisted against the quote and copied to the order via a sales_model_service_quote_submit_before observer, so warehouse and counter staff see exactly when each customer is coming.

This is honest build-to-order software, not an instant Adobe Commerce Marketplace download. ECOSIRE develops the module under app/code/Ecosire/StorePickup, wires it through di.xml, plugins/interceptors and observers, then installs it on your Magento Open Source or Adobe Commerce instance — including data migration of your branch list and setup:upgrade/setup:di:compile on your staging environment first.

You get clean service contracts (repository + data interfaces) for locations and slots, REST and GraphQL endpoints so headless/PWA Studio storefronts can read availability, admin ACL-gated grids for managing branches and bookings, and a cron job that prunes expired slot holds. Everything is delivered as readable, upgrade-safe code you own — no encrypted blobs, no per-seat licensing. We hand over the source, a short runbook, and stay on to support and extend it.

What you get

Custom Magento 2 module Ecosire/StorePickup installed under app/code (or as a Composer package) on your store

Store-pickup carrier, checkout time-slot UI, Google Maps locator and admin location/booking grids configured for your branches

Service contracts (repository + data interfaces) plus REST and GraphQL endpoints for locations and slot availability

Database schema (declarative schema XML) for locations, hours, holidays and slot reservations, with data patches to import your branch list

Admin ACL, system configuration section and cron job for expired-slot cleanup

Installation on your staging environment, setup:upgrade / setup:di:compile run, and verified checkout-to-order flow before go-live

Source code handover, a short operations runbook and a post-launch support window

Who this is for

Omnichannel retail manager

Runs an online store plus several physical branches and wants click & collect that customers actually trust — real opening hours, real slots, and orders that show staff exactly who is coming and when.

Magento merchant / store owner

Wants BOPIS revenue without paying a developer to glue together a generic marketplace plugin; prefers a fixed-scope build installed and supported by one team that owns the code.

Ecommerce developer / agency lead

Needs an upgrade-safe module that follows Magento conventions (di.xml, service contracts, plugins, GraphQL) so it survives Magento and Adobe Commerce upgrades and integrates with a headless or PWA Studio front end.

How Store Pickup / Click & Collect (BOPIS) for Magento 2 Compares

Criterion	ECOSIRE	Custom Build	Competitor
True store-pickup shipping method at checkout (no fake-address workaround)	Included	Partial support	Included
Per-location time-slot scheduling with capacity limits	Included	Partial support	Partial support
Google Maps store locator integrated with checkout	Included	Partial support	Included
Built, installed and supported on your store by one team	Included	Partial support	Not included
Tailored exactly to your branches, hours and capacity rules	Included	Included	Not included
REST + GraphQL availability for headless / PWA Studio	Included	Partial support	Partial support
Full source ownership, no per-seat or recurring license	Included	Included	Not included
Instant self-serve download and install	Not included	Not included	Included

Frequently Asked Questions about Store Pickup / Click & Collect (BOPIS) for Magento 2

Is this an instant download from the Adobe Commerce Marketplace?

No. This is a build-to-order extension. ECOSIRE develops the Ecosire/StorePickup module to fit your store, installs it on your Magento Open Source or Adobe Commerce instance, imports your branch list and verifies the full checkout-to-order flow. There is no instant Marketplace download or self-serve install — we deliver and configure it for you.

How long does delivery take?

Typical lead time is about 2 to 3 weeks from kickoff: requirements and your branch/hours data in week one, build and staging install in week two, and go-live plus verification after your sign-off. Heavily customized capacity rules, multi-warehouse logic or PWA Studio integration can extend this — we confirm a firm timeline in writing before starting.

Does it work with Adobe Commerce as well as Magento Open Source?

Yes. The module uses only standard Magento 2 framework concepts — carriers, di.xml, service contracts, observers, ACL, GraphQL and declarative schema — so it runs on both Magento Open Source and Adobe Commerce. Where Adobe Commerce adds features such as native MSI source assignment or B2B, we can align pickup locations with your inventory sources during the build.

Will it survive Magento upgrades, and is ongoing support included?

Because everything lives in its own module under app/code and uses plugins/interceptors rather than core edits, it is upgrade-safe. We include a post-launch support window, and you can keep ECOSIRE on a maintenance arrangement for Magento/Adobe Commerce version bumps, bug fixes and new features. You receive the full source, so any Magento developer can also maintain it.

Can headless or PWA Studio storefronts use it?

Yes. Locations and slot availability are exposed through both REST and GraphQL, and the booking is written to the quote through service contracts, so a Luma theme, a custom front end or a PWA Studio storefront can all read availability and submit a pickup selection. We tailor the GraphQL schema to your front-end needs during the build.

Do you support multiple stores, websites and currencies?

Yes. Configuration is scoped through system.xml so you can enable pickup per website or store view, assign different branches and hours to each, and respect Magento's existing multi-store, multi-language and multi-currency setup. The store locator and slot rules follow the active store scope.