Case study / Consumer platforms / Corporate gifting

Linden Square: a B2B corporate gifting platform built for one buyer and hundreds of recipients

Linden Square runs corporate gifting: one company buys, hundreds of people receive. Logic Square built its B2B platform, later renamed Tulalo. A Client Portal where a company sets up a gifting order and uploads recipients in bulk. An Admin Portal where Linden Square’s team runs fulfillment. A guest checkout for one time buyers, and a short step for recipients to confirm their details. Per recipient tracking and consolidated invoicing tie it together. Delivered and in production.

Screenshot to be added: Client Portal order setup (demo data only)
CLIENT PORTAL / ORDER SETUP
Client
Linden Square (the B2B product was later renamed Tulalo)
Sector
Corporate gifting, B2B commerce
Build
Client Portal, Admin Portal, guest one time checkout, recipient detail confirmation
Status
Delivered, in production

01 / The Challenge

The order model is the hard part, not the storefront

Normal e commerce assumes one buyer, one recipient, one address, one tracking number. Corporate gifting breaks every one of those: one buyer, hundreds of recipients, hundreds of addresses, hundreds of deliveries that all belong to one order and one invoice. Bolting that onto a standard cart produces a spreadsheet beside the website, which is where the client was.

Linden Square already had a consumer store. Business buyers needed something else entirely.

02 / The Decision

Model one to many, then give each party its own door

The order became a campaign: one buyer, one budget, one invoice, many recipients, each with their own delivery and status. From that model the doors follow. The corporate client needs to set up the order, upload recipients and watch fulfillment. Linden Square’s own team needs one place to run every client’s orders. A company sending gifts once needs to pay without opening an account. And the recipient needs one short step to confirm where the gift should go, nothing more.

03 / What We Built

Client Portal, Admin Portal and guest checkout on one order model

How an order moves through the platform

  1. 01

    Client sets up the order.

    In the Client Portal: branding, the gift, the budget.

  2. 02

    Recipients uploaded in bulk.

    CSV upload with validation, so bad addresses and duplicates are caught before anything ships.

  3. 03

    Recipients confirm details.

    A short, branded page where each recipient confirms delivery details. One step, not a portal.

  4. 04

    Linden Square fulfills.

    In the Admin Portal, the team sees every client’s orders and runs fulfillment, with each recipient’s delivery tracked individually.

  5. 05

    One invoice.

    Account clients get consolidated invoicing against stored billing profiles; one time buyers pay by card through guest checkout.

Diagram to be added: one buyer node fanning out to many recipient nodes, all converging back to one invoice, with the Admin Portal drawn alongside the fulfillment step
FIG. 01 / ONE BUYER, MANY RECIPIENTS, ONE INVOICE

Bulk upload with validation

Recipient lists arrive as spreadsheets. The platform validates them on the way in rather than discovering the errors at the courier.

Screenshot to be added: Bulk recipient upload with validation (demo data only)
BULK UPLOAD

Per recipient tracking

Each delivery carries its own status inside the order, so the buyer can answer “did Priya get hers” without a phone call.

White label branding

The recipient sees the buying company’s brand, not the platform’s.

Screenshot to be added: Recipient confirmation page (demo brand)
RECIPIENT CONFIRMATION

The Admin Portal

Linden Square’s team works every client’s orders from one place: order status, recipient lists, fulfillment and invoices.

Screenshot to be added: Admin Portal order view (demo data only)
ADMIN PORTAL / ORDER VIEW

Billing for two kinds of buyer

Account clients keep stored billing profiles and get consolidated invoices across orders. A company sending gifts once checks out as a guest and pays by card, no account needed.

Screenshot to be added: Invoice view (demo data only)
INVOICE VIEW

04 / Engineering Notes

One order, many deliveries, one truth

The campaign is the aggregate. Recipients, deliveries and statuses hang off one order record so the invoice and the tracking never disagree.

Validation at the edge. Bad data is rejected at upload, the cheapest point to catch it.

Three doors, one model. The Client Portal, the Admin Portal and guest checkout are views on the same order record, so the client, the operator and the one time buyer never see different numbers.

Account and guest payments side by side. Stored billing profiles and consolidated invoicing for repeat clients, card payment for guests, on one billing model.

05 / The Results

Delivered, in production, running the one to many model

  • Delivered and in production as Linden Square’s B2B gifting platform, now known as Tulalo.
  • One to many gifting operational: order setup, bulk recipient upload with validation, recipient detail confirmation, per recipient tracking.
  • Two kinds of buyer served: account clients with stored billing profiles and consolidated invoicing, one time buyers through guest checkout.

Have a business model normal e commerce does not fit?

Book a Strategy Call

06 / Who this pattern fits

Any business where one purchaser pays for many recipients: corporate gifting and bulk gifting programs first, then employee rewards and recognition, onboarding kits, event gifting, incentive programs, company stores.

The tell is a spreadsheet of names sitting next to the website. It fits especially well when a business already runs a consumer store and needs a separate B2B side with its own order model. The data model fixes that, not the storefront. For a two sided consumer platform instead, see Grouped, a two sided fan platform. More on consumer platform operations.

FAQ

Common questions

What is a corporate gifting platform?

Software where a company sets up a gifting order, uploads many recipients at once, tracks every delivery and gets one invoice, while the gifting business runs fulfillment from an admin side. Linden Square’s B2B platform is one, built by Logic Square.

Why does bulk corporate gifting need more than standard e commerce?

Standard carts assume one buyer and one recipient per order. Corporate gifting is one buyer and hundreds of recipients per order, which changes the order model, the address handling, the tracking and the invoice.

What did Logic Square build for Linden Square?

The B2B side: a Client Portal for corporate buyers, an Admin Portal for Linden Square’s team, a guest one time checkout, a short recipient detail confirmation step, bulk upload with validation, per recipient tracking, stored billing profiles and consolidated invoicing. Linden Square’s consumer store predates our work and is not ours.

What is Tulalo?

The later name for Linden Square’s B2B gifting product, which Logic Square built. It was renamed to keep it distinct from Linden Square’s consumer store.

How do one buyer and many recipients change the data model?

The campaign becomes the aggregate: one order with many deliveries, each with its own address and status, rolled up to one invoice. Get that wrong and the invoice and the tracking drift apart.

Why is guest checkout part of a B2B gifting platform?

Because plenty of companies send gifts once a year. Making them open an account loses the order; guest checkout takes the card and keeps the same order model behind it.

How are branded gifting portals different from a company store?

A company store sells items to employees who pay. A gifting portal sends chosen gifts to recipients who do not. The buyer, the payer and the recipient are different people, and the platform has to know which is which.

Can the same model support employee rewards, client gifting and event programs?

Yes. Each is one purchaser and many recipients with a branded experience and tracking; the order model does not care why the gift is sent.

A business model normal e commerce does not fit?