E-commerce & Retail · Specialist gift commerce

Connecting a date-specific gift purchase to the item that ships

A specialist gift retailer connected date-based publication search, limited inventory, personalization, payment, and shipping while moving historical records to a new data platform.

  • Date-based search
  • Unique inventory
  • Personalized orders
  • Data migration

The business context

The meaningful date was part of the product.

For a retailer selling historical publications as gifts, a shopper’s starting point might be a birthday or anniversary. Publication type and region also mattered, and stock depended on the particular edition available. This was a different purchase from choosing a standard product that could be replenished indefinitely.

Working through an IT services partner, Shinetech helped rebuild the commerce experience and its operating data. The scope connected the shopper’s search with presentation options, personalized details, payment, order processing, and shipment. Earlier orders and customer records also needed to remain useful after the move.

Reconstructed gift storefront with date-based publication results, availability, and personalized presentation options.
System view

Finding a publication for a meaningful date

Invented publication covers, dates, stock states, and gift choices illustrate the buying task. No real publication, retailer, or customer order is shown. View full-size interface (new tab)

The operating challenge

A correct checkout still needed to produce the correct physical gift.

The selected date, publication, and availability had to remain clear as the buyer moved from results to product details and checkout. Gift presentation and personalization added information that fulfillment needed alongside the purchased item. Losing those details between storefront, payment, and order handling would undermine the sale.

The old SQL tables held products, orders, order lines, contacts, and mailing information. Migrating those records meant reconciling relationships, statuses, and historical field meanings with a new Dataverse model. Copying individual rows was not enough to preserve an intelligible order history.

The delivery decisions

Preserve the selected item through each commercial handoff.

  1. Start with the business records and their relationships

    The team established Dataverse models for products, orders, order lines, contacts, discounts, and shipping information. Migration mappings and dataflows connected the legacy SQL records to those structures before the surrounding experience was completed.

  2. Build discovery around the way buyers choose the gift

    Power Pages supported filtering by date, publication type, and region, with availability, pagination, and product details. Presentation options and personalization continued into the cart and checkout, keeping the buyer’s selection connected to the order.

  3. Validate payment and shipping as separate handoffs

    Payment providers, order processing, amount calculations, and postal services were integrated in stages. Power Automate and Dynamics 365 extensions supported the operational work, while two Power Apps supported order management, reconciliation, and data comparison.

The working detail

Go-live exposed maintenance responsibilities as well as customer journeys.

A documented operating handoff

A gap in certificate-maintenance knowledge required the team to reconstruct the certificate and custom-domain update process. Restoring HTTPS service and documenting that work made a recurring operational responsibility explicit.

The platform entered production with follow-on support for checkout, shipping, and reporting. That continuing work mattered because the business outcome was an order that could be processed and delivered, not merely a finished storefront. The documented result is the connected capability; no conversion-rate or revenue improvement is claimed.

The delivered result

A date-specific purchase could continue through an operating commerce workflow.

Connected checkout

Search, availability, presentation choices, and payment were brought together.

Usable operating data

Legacy records were mapped into the new platform with their relationships.

Production support

The live site continued into post-launch support and iteration.

The system is live. Store performance, sales growth, and inventory-concurrency guarantees are outside the verified project evidence.

Case taxonomy

Searchable by industry, technology, product, and business need.

Industry and product

  • E-commerce & Retail
  • Specialist gift commerce

Technology and delivery

  • Power Pages
  • Dataverse
  • Power Automate
  • Dynamics 365

Business need

  • Date-based search
  • Unique inventory
  • Personalized orders
  • Data migration

Discuss your project

Does your checkout preserve the details your fulfillment team needs?

Tell us how your business works and where your software needs to change.

Talk to our team

Get in touch

Ready to build software that fits your business?

Tell us what you need to build, modernize, automate, or augment with AI. We can start with a focused discussion or a no-risk 1-week trial.

“A fantastic company to work with.” After the initial rapid development project, American Shipping Co. kept two Shinetech developers embedded for nearly four years, supporting internal and external tools and new AI initiatives.
Marc Greenberg testimonial portrait Marc GreenbergCEO, American Shipping Co. - 5-star Google Review

Response within 1 business day.