Case studies / Selected work

Inside the work.
Behind the experience.

Two production workstreams. One connected manufacturing environment. These stories describe complementary workstreams for the same industrial manufacturer, connecting commerce, content, customer inquiries, and production operations.

Conceptual glass structures connected by illuminated pathways
Commerce, content, and connected operations.
Built around the realities of industrial business.

01 / Industrial manufacturing

Commerce improvements across
the buying journey.

A continuing series of production improvements connected ordering rules, catalog publishing, ERP account data, and operational visibility in an existing B2B commerce environment.

  • Production workstream
  • Znode · ERP-connected workflows
Illustration of an industrial distributor handing a tray of fittings to a customer
Quick ordering brings a familiar trade-counter task into the storefront: identify the part, check the quantity, and build the order.

The business context

An industrial order can begin with a known part number, a product page, or a repeat visit to the cart. Each route still needs to respect the same minimums, manufacturing increments, and inventory limits. Behind that purchase, catalog publishing and account data need to stay useful to the people who maintain them.

GCG’s responsibility

GCG delivered application changes and production releases across these connected workflows. The work extended from storefront behavior into catalog publishing, selected ERP-connected account workflows, operational notifications, and release handling.

Precision industrial components and a cutaway valve in an original conceptual illustration

Make buying rules consistent

We improved manually entered and suggested SKU handling in Quick Order, clarified inventory messages, and prevented unavailable selections from reaching Add to Cart. Quantity validation across product pages, the cart, and quick-order entry points was updated to handle minimums and manufacturing increments consistently, including make-to-order and limited-inventory conditions.

Connect merchandising with published data

We aligned sitemap generation with published catalog data and improved how category publishing carries SEO information into sitemap output. Category ordering corrections also helped curated priority products retain their intended position. These changes connected everyday catalog maintenance with the storefront behavior it controls.

Improve the operational edges

We corrected a shipping-address workflow that could create invalid placeholder contacts in the ERP, and added response details to failed ERP resend notifications. Related releases improved deployment handling and enabled required marketing measurement resources while checking representative storefront pages.

Illustrative reconstructionFictional sample data / Explanatory sketch
Quick Order / One line, several rules

Build an order line

Product
PART-A12
Sample industrial partSKU recognized
Quantity entered
10
10 does not meet the minimum. Use 12 or another valid increment.
Cart actionAdd to cart
Minimum quantity: 12Order increment: 6Inventory: Available for this example
A valid next quantity12
Recognizing the SKU does not make every quantity orderable. Validate the product, quantity rules, and availability together before the cart action becomes available.
  1. Identify the product
    The typed SKU resolves to the intended sample product.
  2. Explain the conflict
    The entered quantity is below the minimum and does not meet the increment rule.
  3. Offer a useful correction
    Twelve is valid in this fictional example. The buyer can see a concrete next step.
Illustrative reconstruction of inline Quick Order validation. PART-A12, the quantities, and the availability label are fictional sample data. The drawn controls are explanatory, not a working order form.

A more dependable set of daily workflows

The delivered changes made ordering rules more consistent, aligned sitemap output with published data, corrected an account-data edge case, and gave operations more useful failure context. The result is demonstrated through specific production behavior across the buying and maintenance journey.

Explore industrial ordering rules

02 / Industrial manufacturing

CMS modernization with
business workflow validation.

A Sitefinity upgrade brought application modernization together with publishing, documents, customer inquiries, and a controlled production release.

  • Production workstream
  • Sitefinity · HubSpot forms
Illustrated engineering workspace with technical drawings, a tablet, and a sample component
Technical information is part of the customer journey, from understanding a product to starting an inquiry.

The business context

A manufacturer’s website serves several jobs at once. Marketing needs to publish confidently. Customers need technical content and a working path to request a quote. Internal teams need those inquiries to reach the next step. An application upgrade has to account for that connected experience.

GCG’s responsibility

GCG delivered the production CMS upgrade and an updated request-for-quote form, addressed the form’s verification and browser-policy dependencies, and validated public, editorial, and inquiry workflows. Release preparation included recovery readiness and documented go/no-go checks.

Illustration of industrial product content being photographed in a studio

Prepare the release and its recovery path

The deployment record identified the approved application artifact and confirmed the recovery database was available. Preparation also covered the prior application, configuration, and relevant media, along with a content freeze and the people responsible for deployment, validation, approval, and rollback. Recovery planning treated these pieces as a matched set.

Validate what people actually do

Checks covered public pages and documents, existing content and media, CMS administration, page preview, and publishing. The updated quote form was checked for required fields, file upload, privacy consent, verification, and submission. Controlled test submissions provided evidence that the inquiry reached its expected downstream result, and representative lookup was also checked.

Carry the learning into ongoing maintenance

Form-rendering and verification dependencies were resolved as part of the upgrade work and captured in deployment guidance. A later maintenance release checked public content, administration, form rendering, and representative lookup again. Its read-only checks were recorded separately from the earlier submission validation.

Illustrative reconstructionFictional sample data / Explanatory sketch
CMS release / Workflow review sheet

Follow the work through the upgrade

Editorial

  • Authoring opens
  • Preview represents the draft
  • Publishing follows the intended path
Review plus controlled authoring and publishing checks

Public experience

  • Pages and navigation
  • Published documents
  • Lookup experience
Read-only visitor checks

Form workflow

  • Form renders
  • Verification behavior
  • Controlled submission and response
Rendering checks and separately controlled test submissions
Record what was checked and how.
A visible form is evidence that it renders. A successful controlled submission tests a different part of the workflow. Keep those conclusions separate in release evidence.
  1. Start with the author
    The team must be able to create, preview, and publish useful content.
  2. Follow the visitor
    Public pages, documents, and lookup paths deserve their own validation.
  3. Distinguish the test
    Read-only inspection and controlled workflow tests answer different questions.
Illustrative reconstruction of a CMS validation worksheet. The lanes show types of review, not a checklist asserting that every check passed in a specific deployment.

A production upgrade evaluated through business continuity

The upgraded platform retained the documented content, editorial, and inquiry workflows. Release evidence connected application health with the tasks that matter to marketing and customers, while keeping recovery preparation and the limits of each validation pass visible.

Explore CMS upgrade validation

Engineering insights

Making integration
understandable.

Explore a non-production implementation of an administration experience that connects integration activity to business records. This technical article includes a reconstructed interface and explains the limits of the evidence shown.

Read the engineering article

Bring your environment into the conversation

What needs to work better
behind your next experience?

We help manufacturers and distributors connect the customer journey to the systems and workflows that make it possible.

Start a conversation

Client identities and identifying project details are withheld. Images are original conceptual illustrations, not client photographs or screenshots. Each story states its delivery status; outcomes are limited to the work described. The two production stories above describe complementary workstreams for the same industrial manufacturer.