Gibbys operates a large e-commerce store with thousands of electronics products, changing inventory, promotions, pricing rules, and a steady flow of real customer orders.

The platform needed constant development as the business changed: new features, improvements to existing flows, fixes, and changes to how products and promotions were presented and managed. Because the store was already live and generating revenue, those changes had to be made without disrupting existing functionality or the customer experience.

• Full-stack development across the entire e-commerce platform: Worked across essentially every part of the WordPress/WooCommerce store, from backend business logic and administration to the customer-facing shopping experience.
• Product and catalog functionality: Built and extended functionality around products, categories, filtering, search, product data, pricing, availability, and the way a large electronics catalog was presented and managed.
• Cart, checkout, and ordering: Worked on the flows that turned browsing into actual transactions, including cart behavior, checkout functionality, order handling, and the business rules around them.
• Promotions and commercial features: Built functionality around sales, discounts, promotions, product bundles, pricing rules, and other features driven by the retailer's day-to-day commercial requirements.
• Custom WordPress and WooCommerce development: Built numerous custom WordPress plugins and extended WooCommerce with custom PHP, hooks, backend logic, and purpose built functionality where existing plugins were not enough.
• Administration and internal tools: Built and modified backend functionality used to manage products, orders, promotions, content, and other operational parts of the store.
• Performance and production work: Diagnosed slow queries, frontend bottlenecks, bugs, and production issues on a large live store where changes affected real customers and orders.
• Ongoing feature development: Worked directly from real business requirements, continuously adding, changing, and maintaining functionality as the retailer's needs evolved.

Working on a live store. This was a production e-commerce site with real customers and real orders, so even small changes could have consequences. Anything touching products, pricing, cart behavior, checkout, or orders had to be tested carefully because breaking one of those flows meant affecting the actual business.

Working inside a large existing codebase. The platform had years of existing functionality, custom code, plugins, WooCommerce behavior, and business rules built on top of each other. Before changing something, I often had to trace through several parts of the system to understand what depended on it and what else the change might affect.

WooCommerce gets complicated quickly. Products, variations, promotions, taxes, shipping, stock, carts, and orders are all connected. A change that looked isolated could affect several other parts of the store, especially once custom plugins and retailer-specific rules were involved.

Performance on a large catalog. With a large number of products and a heavily customized WordPress installation, inefficient queries or expensive backend logic became noticeable quickly. Finding and fixing bottlenecks meant understanding both the custom application code and how WordPress and WooCommerce behaved underneath it.

Work shown here relates to Gibbys' previous WordPress/WooCommerce platform, which was the live production system during my involvement. The retailer has since migrated to Shopify.

• Kept a major e-commerce operation moving: New features, fixes, and improvements could be shipped continuously without disrupting a store that was already serving real customers and processing orders.
• Turned business requirements into working features: Promotions, product functionality, checkout changes, internal tools, and other commercial needs could be implemented directly in the platform as the business evolved.
• Extended the platform beyond standard WooCommerce: Custom plugins and purpose built functionality allowed Gibbys to support workflows and features that were specific to the business rather than being limited to what existing plugins could provide.
• Improved performance and reliability: Fixing bottlenecks, production issues, and inefficient parts of the system helped keep the shopping experience stable as the catalog and platform grew.
• Reduced the risk of changing a mature system: Deep familiarity with the existing codebase made it possible to make substantial changes without repeatedly breaking unrelated parts of the store.