Shopify Technical Support & Store Operations

Problem

The store’s technically complex wallbox products required a clearer way for prospective customers to compare models without navigating between multiple product pages.

Solution

I built a Shopify comparison interface that allows two wallbox models to be selected independently and presents their product media, pricing, purchase links, embedded videos, and technical specifications together.

How I built it

I used structured Shopify product data and metafields instead of hard-coded comparison content. This keeps the feature scalable and allows the merchant to maintain product information through Shopify Admin without rewriting the section.

Result

The comparison experience has been implemented and prepared for launch. It enables prospective customers to evaluate two products within one interface while allowing the merchant to manage the underlying comparison information through Shopify’s product-management workflow.

Problem

Products with multiple model and color combinations required different image sets. As more configurations are added, a single product could ultimately contain hundreds of media files. Loading and displaying the entire product media library on the initial page view would create an overwhelming gallery and could unnecessarily increase the amount of media the storefront needs to process.

Solution

I created a variant-specific gallery that displays only the image set assigned to the active model and color combination.

How I built it

I created and configured a variant metafield that stores the image set assigned to each product variant. In the product gallery’s Liquid code, I replaced the standard loop through the entire product.media collection with a loop through the images provided by the active variant’s metafield. I stored the image relationships at variant level rather than relying on filenames or filtering the complete media library, giving the merchant direct control through Shopify Admin.

Result

The variant-specific gallery has been implemented and tested in the pre-launch storefront. It is prepared to show prospective customers a focused set of images corresponding to their selected model and color combination, without presenting the product’s complete media library on first load.

Problem

The original newsletter popup provided limited space for presenting the offer, collecting additional customer information, and explaining how submitted information would be used. The store required a dedicated experience that could support richer content without interrupting normal storefront browsing.

Solution

I created a custom full-screen Liquid section for a standalone newsletter page with a focused signup experience and richer customer fields.

How I built it

The section supports a merchant-selected image, editable heading and introductory text, configurable colors, optional social links, and an @app block for embedding the newsletter form. I added responsive styling for a split desktop layout and full-width mobile form, plus JavaScript that sequences the form and image reveal while respecting reduced-motion preferences. I used an app block instead of hard-coding a form provider so the layout remains reusable and the form can be managed independently.

Result

The dedicated newsletter page has been implemented and tested in the pre-launch storefront. It is prepared to present the signup offer in a focused layout, support richer customer fields, and provide a responsive experience across desktop and mobile devices.

Problem

The store was being prepared to serve customers across multiple European countries. It required country-specific languages, currencies, domains, and localized URLs without creating and maintaining a separate Shopify store for every market.

Solution

I configured a centralized Shopify Markets structure for 17 country-level markets with localized domains, language subfolders, currencies, and translated storefront content.

How I built it

I assigned the appropriate currency, domain, and language settings to each market, configured the German and international domains, created localized language subfolders, and enabled regional currency presentation including euros and British pounds. I configured the connected translation app for supported product and storefront content, then tested the market selector. I used Shopify Markets instead of separate stores so product and theme management remain centralized while each market receives an appropriate language, currency, and URL structure.

Result

The international market structure has been configured and tested for the pre-launch storefront. The store is prepared to deliver localized regional experiences across the configured European markets while maintaining a centralized Shopify catalog and theme.

Problem

Because the storefront was still being prepared for launch, it needed a structured way to present available product and business reviews at important decision points. The system also needed to support future review collection, moderation, media uploads, and consistent branding.

Solution

I configured complementary Judge.me product-review and Google Business review experiences across product pages, collections, and the homepage.

How I built it

I installed and configured Judge.me for product reviews, moderation, verification indicators, star ratings, customer media, and review-request emails. I added its review widget to the product template and a card carousel to the homepage, then styled the widgets and emails to match the store. I connected the Google Reviews integration to the managed Business Profile and added a storefront business-rating section. I kept product-specific and business-level reviews as separate sources while using configurable app blocks rather than hard-coded review content.

Result

The review system has been configured and tested for the pre-launch storefront. It is prepared to display product and business-level social proof, collect future customer reviews, support photo and video submissions, and provide moderation controls after launch.

Problem

The pre-launch store contained a growing catalog of physical products, accessories, wallbox mounting solutions, and digital products. It required a consistent organizational and data structure so products could be assigned to the correct collections, enriched with structured information, and presented in a controlled order without manually rebuilding collection contents whenever products were added.

Solution

I created and organized the Shopify product catalog using structured listings, automated collections, curated ordering, metafields, and reusable metaobject records.

How I built it

I maintained product information, variants, media, tags, and manufacturer data; used product and collection metafields for attributes, collection configuration, and filtering logic; and used metaobjects for reusable records referenced by multiple products. I created automated collections using tags and manufacturer conditions, then reviewed selected products, arranged storefront order, and assigned collection metafields. I separated classification, structured data, and reusable content across tags, metafields, and metaobjects while retaining manual merchandising control where needed.

Result

The product catalog, structured data, and collection architecture have been configured and reviewed for the pre-launch store. The setup is prepared to keep products organized as the catalog grows while supporting reusable content, curated collection pages, and relevant collection-specific filters.

Problem

Shopify orders, eBay orders, order statuses, and inventory information needed to be handled through a centralized operational system. Managing each sales channel independently would create fragmented order handling and increase the need to transfer information manually between platforms.

Solution

I connected Shopify and eBay to Billbee so the company could retrieve orders through one operational workspace and synchronize relevant status information with the connected sales channels.

How I built it

I personally authorized both channel connections inside Billbee, configured scheduled automatic order retrieval, and enabled order-status synchronization between Billbee and the connected platforms. For Shopify, I reviewed the available connection settings and confirmed that imported orders could supply Billbee with the operational information needed for downstream processing.

Result

The pre-launch system now has a tested multichannel foundation in which Shopify and eBay orders can enter Billbee automatically instead of requiring manual order creation. The Shopify connection serves as the starting point for the document and fulfillment workflow demonstrated in the following chapters.

Problem

Creating an invoice and delivery note manually for every imported order would be repetitive and could lead to delayed documents, inconsistent routing, or duplicate generation.

Solution

I created a four-rule Billbee automation chain that generates and distributes the required documents when an imported order meets the paid-order condition.

How I built it

The first rule responds to a paid order imported through a shop connection, creates the invoice, saves the PDF, triggers email delivery, and checks that an invoice has not already been created. The second rule responds to the invoice email trigger and sends the document to the customer through the designated email template. The third rule creates and stores the delivery note for the same qualifying imported order, triggers its email delivery, and prevents duplicate creation. The fourth rule sends the delivery note to the client's designated internal address. I created and tested all four rules; they run without a manual approval step and do not change the order status.

Result

A qualifying Shopify order can trigger invoice and delivery-note creation and routing without manual document preparation. Duplicate-prevention conditions protect the workflow from generating the same document more than once.

Problem

Generating documents was only part of the process. The invoice still needed to reach the customer, the delivery note needed to reach the client, and both documents needed to be filed consistently for later access.

Solution

I created separate email-delivery templates and connected Billbee directly to Google Drive for automatic document archiving.

How I built it

I wrote German email templates for the customer invoice and internal delivery note and used Billbee's {OrderNumber} placeholder to identify the relevant order. Gmail serves as the sending service, and the corresponding document PDF is attached automatically when the email rule runs. I configured Google Drive as a Billbee cloud-storage destination and created separate folders for invoices and delivery notes. Billbee saves the generated PDFs with structured filenames, producing an organized document history without requiring staff to download, rename, and upload each file manually.

Result

Generated invoices and delivery notes can be distributed and archived automatically. The workflow creates a consistent record of test documents and reduces repetitive document-handling steps in the pre-launch operation.