A GraphQL-only Adobe Commerce backend for a headless PWA storefront in Saudi Arabia — no classic theme at all — centred on a drag-and-drop homepage builder.
No Luma theme: every customer-facing page comes from the PWA.
Drag-and-drop banners, products, categories and CMS blocks.
Physical stores and per-product availability over GraphQL.
Dropped product options traced to the cart-mutation resolver.
Linked to the products they cover and added alongside them.
The PWA is the storefront; Magento serves it entirely through an extended GraphQL schema.
The customer never touches a Magento template: every page in the PWA is built from GraphQL responses.
Extended across catalog, customer, checkout, store config, compare list, wishlist, reviews and product alerts.
A drag-and-drop homepage/dashboard builder exposed through a composite GraphQL resolver.
Physical store CRUD plus per-product store availability over GraphQL.
Warranty products linked to the products they cover and added to the cart alongside them.
A configurable brand-logo slider exposed over GraphQL.
A back-in-stock “notify me” mutation.
Tabby buy-now-pay-later merchant configuration exposed via the StoreConfig GraphQL type.
Estimated-delivery and pre-order fields on products, review averages, category promotion banners, and a compare list capped at 4 products.
An in-stock layered-navigation filter on Elasticsearch.
A social-login mutation, plus header/footer blocks, an announcement bar, a minimum order amount and a newsletter-unsubscribe mutation.
The homepage is composed in the admin and delivered to the PWA through a single resolver.
Banner, product, category and CMS-block sliders are placed in the drag-and-drop builder.
One composite GraphQL resolver returns the whole layout.
The PWA draws the homepage from that response.
With no theme to fall back on, every feature and every bug lives in GraphQL.
Customisable product options were dropped on add-to-cart — but only through GraphQL.
Traced it to the cart-mutation resolver rather than the cart logic, and fixed it with a narrowly scoped override.
Options reach the cart from the PWA, with the underlying cart logic untouched.
The PWA needed every storefront feature over GraphQL.
Extended the schema across catalog, customer, checkout, store config, compare list, wishlist, reviews and product alerts.
With no theme layer, homepage content still had to be arranged in admin.
A drag-and-drop builder delivered through a composite GraphQL resolver.
How the hardest calls were made: what else was on the table, why it lost, and what the chosen design costs.
Customisable options vanished when products were added to cart through the GraphQL mutation, but worked in the classic storefront — so the bug lived in the GraphQL path.
Kept the fix as small as possible, applied where the option data was dropped, so every GraphQL client gets correct cart behaviour.
Even a narrow override needs re-checking when Magento changes that class, so the reason for it has to be documented.
GraphQL-only backend with no classic Luma theme; the customer-facing frontend is a separate PWA.
Drag-and-drop homepage/dashboard builder exposed through a composite GraphQL resolver.
Extended the GraphQL schema across catalog, customer, checkout, store config, compare list, wishlist, reviews and product alerts.
GraphQL store locator (store CRUD plus per-product availability) and warranty products attached to the items they cover.
Fixed customisable options being dropped on add-to-cart, traced to the cart-mutation resolver.
Brand-logo slider, back-in-stock “notify me” mutation, and Tabby merchant config exposed via StoreConfig.
I'm available immediately for senior Adobe Commerce roles and contract work. Tell me what you're building.