Gent Hulaj

01

Sales Agent

b2b

Lets a sales representative work inside a customer's account — building and placing an order on their behalf, with the agent recorded on the order.

Wholesale accounts do not self-serve. Orders arrive by phone and email, and someone has to enter them against the right account, at the right pricing, without handing that account's credentials around.

Extension point

Custom entity and admin module, storefront context switching, order attribution

Written in

PHP, Symfony, Shopware Administration (Vue), MySQL

02

Curbstone Payments

payments

↳ Curbstone

Payment handler integrating Curbstone's gateway, so card data is tokenised remotely and never lands on the merchant's infrastructure.

Curbstone is a PCI-validated Level 1 service provider. Routing card capture through remote tokenisation keeps the store's own systems out of PCI scope — which matters far more to a merchant than a few lines of checkout code.

Extension point

Payment handler, order transaction state machine, checkout finalisation

Written in

PHP, Symfony, REST, Shopware payment API

03

Smarty Address Validation

checkout

↳ Smarty (formerly SmartyStreets)

Validates and normalises US addresses at checkout against USPS CASS-certified data, with autocomplete as the customer types.

For a regulated shipper a wrong address is not a missed delivery, it is a compliance exposure. Smarty also returns whether an address is residential or commercial and whether it is deliverable at all, which is what decides the carrier and service level downstream.

Extension point

Checkout address validation, storefront JS, cart error handling

Written in

PHP, Symfony, JavaScript, REST

04

ShipHero Warehouse Integration

fulfilment

↳ ShipHero

Two-way sync with the ShipHero warehouse management system: orders out for fulfilment, stock levels and tracking numbers back in.

Once fulfilment moves into a real WMS, the storefront stops being the source of truth for stock. Orders have to reach the warehouse reliably and inventory has to come back, or the catalogue starts selling things that are not there.

Extension point

Scheduled tasks, message queue, GraphQL client, webhook endpoints

Written in

PHP, Symfony, GraphQL, Message queue, MySQL

05

NMI Payments

payments

↳ NMI

Payment handler for the NMI gateway, with card details tokenised in the browser so they never reach the store's servers.

A merchant needs more than one route to take money. Gateways go down, rates get renegotiated, and a high-risk category can lose an account with little notice — so the store has to be able to switch or run two in parallel.

Extension point

Payment handler, browser-side tokenisation, order transaction state machine

Written in

PHP, Symfony, JavaScript, REST

06

Authorize.Net Payments

payments

↳ Authorize.Net

Payment handler for Authorize.Net, again tokenising in the browser and keeping the merchant out of PCI scope.

Authorize.Net is what a lot of established US merchants already process on. Meeting them where they are is faster and cheaper than asking them to migrate their processing to suit a new storefront.

Extension point

Payment handler, browser-side tokenisation, refunds and capture

Written in

PHP, Symfony, JavaScript, REST

07

Abandoned Cart Saver

revenue

Finds carts left behind after a set interval and emails the customer a link that restores the cart exactly as they left it.

Most carts are abandoned, and a recovered one is the cheapest order a store will take all day. The work is in the details: send once rather than repeatedly, stop the moment the order completes, and restore the cart rather than dumping the shopper on the homepage.

Extension point

Scheduled task, message queue, cart persistence, mail templates, event subscribers

Written in

PHP, Symfony, MySQL, Twig

08

Sales-Channel Specific Content

merchandising

Lets content, product data and category structure differ per sales channel, so one Shopware instance can serve several storefronts without duplicating the catalogue.

A merchant running more than one storefront off one installation still needs each to look and read like its own shop. Forking the catalogue per channel is the obvious move and the wrong one — it doubles the maintenance and the two copies drift apart within a month.

Extension point

Entity extensions with sales-channel association, CMS data resolver, storefront subscribers

Written in

PHP, Symfony, Shopware Administration (Vue), MySQL, Twig

09

Product Bundle

merchandising

Sells several products together as one purchasable bundle, with its own pricing and its own line in the cart.

Bundles raise basket size, but only if the maths is right. The bundle has to price as a unit while still drawing down stock on each component, and it has to survive partial refunds — which is why it belongs in the cart pipeline rather than in a template.

Extension point

Custom entity and admin module, cart data collector and processor, price calculation

Written in

PHP, Symfony, Shopware Administration (Vue), MySQL

10

Shipping Protection

revenue

Adds an optional shipping-protection line item at checkout, priced from the cart total and toggled by the customer.

It gives the customer a remedy when a parcel is lost or damaged, and the merchant a margin line that costs nothing to stock. It has to be added as a real line item so tax, totals, refunds and the order record all stay correct.

Extension point

Cart data collector and processor, custom line item type, storefront toggle

Written in

PHP, Symfony, JavaScript, Twig