ShipNLogic
Expanding the capabilities of a shipping technology platform
Contributed to the development and strategic expansion of a B2B shipping platform through account management improvements, workflow definition, product analytics, integration research and growth strategy.
- Company
- GrandGale Technologies
- Market
- United States
- Product
- Enterprise shipping label purchasing platform
Case Study Contents (11)
Project overview
ShipNLogic is a B2B shipping technology platform developed by GrandGale Technologies for businesses in the United States.
Its primary value proposition is helping businesses purchase shipping labels at competitive rates, manage shipping activities and access shipping-related services. Platform capabilities span account management, shipping label purchasing, carrier and service information, pricing visibility, label management and integrations with external business software.
My documented contributions covered product requirements, account lifecycle considerations, workflow analysis, product analytics planning, design collaboration, integration research and growth strategy—with a recurring focus on ensuring product decisions addressed the wider business and customer problem rather than adding isolated functionality.
The product challenges
As ShipNLogic evolved, several product limitations and expansion questions needed structured product thinking. The original account model was built around company buyers, creating a barrier for individuals who wanted to purchase shipping labels. Existing workflows also raised questions about how account identities should evolve, how shipping label statuses should communicate operational realities and how customer activity could be translated into credible product value.
Beyond core workflows, there were strategic opportunities to expand the integration ecosystem and evaluate more sustainable customer acquisition channels across several dimensions:
- —Customer onboarding and account flexibility.
- —Account lifecycle and historical data continuity.
- —Shipping label workflow clarity.
- —Customer value communication and retention.
- —Integration opportunities and market expansion.
- —Customer acquisition strategy and regulatory risk.
My contribution
I contributed specific product management work across five interconnected areas:
- 01Account expansion and lifecycle management.
- 02Shipping label workflow definition.
- 03Customer value communication and product analytics.
- 04Integration research and ecosystem opportunities.
- 05Growth strategy and customer acquisition research.
Expanding the platform beyond company buyers
ShipNLogic initially operated with a registration model designed around company buyers. A customer requirement surfaced a clear limitation: individuals also needed to purchase shipping labels without registering as a company, which the existing onboarding flow did not adequately support.
I participated in product discussions around expanding the account model to accommodate both individual and company buyers, examining requirements covering:
- —Supporting individual registration without unnecessary company information.
- —Introducing an appropriate signup experience for individual buyers.
- —Accommodating different account identities within the existing platform.
- —Maintaining a consistent core product experience.
- —Avoiding unnecessary duplication of the application.
The individual registration change was discussed as an implemented change in the project record.
The wider product consideration: Account upgrade continuity
Supporting individual buyers raised a related account lifecycle question: what happens when an individual customer later establishes a company and wants to operate through a company account? Requiring an entirely new account risked fragmenting transaction history, disconnecting shipping records, creating duplicate identities and introducing unnecessary onboarding friction.
I developed a Product Requirements Document for a proposed Individual-to-Company Account Upgrade workflow so customers could evolve without losing their existing platform history:
- —An upgrade entry point for individual accounts.
- —Collection of company information.
- —Conversion of the existing account’s purchasing identity.
- —Assignment of company administrator permissions.
- —Preservation of historical labels and transactions.
- —Appropriate account permissions.
- —Clear confirmation and user communication.
Clarifying the shipping label void lifecycle
A proposed enhancement to the label management table involved introducing a dedicated Void Status column. The central workflow challenge was determining what that column should communicate without conflating unrelated operational states.
Printing, shipping and voiding represent distinct operational concepts. For example, a label could be printed before a void request is submitted, and a shipment’s status should not automatically determine whether its label has been successfully voided. Combining them into a single status model risked ambiguity.
I analysed the distinction and helped define a dedicated void lifecycle with four proposed states:
| Status | Meaning |
|---|---|
| Not Voided | No successful void has occurred |
| Void Requested | A void request has been submitted |
| Voided | The void has been successfully confirmed |
| Void Failed | The void attempt was unsuccessful |
The key decision was that Void Status should communicate only the voiding lifecycle—never attempting to represent whether a label has been printed, shipped or delivered. This established clearer terminology for users and operational teams.
Turning product data into customer value: ShipNLogic Wrapped
ShipNLogic Wrapped was conceived as a product analytics and customer retention initiative aimed at reinforcing the value delivered to customers and encouraging continued usage.
Rather than treating it as a collection of decorative statistics, I approached it as a data communication exercise—reviewing the available label management information and helping organise potential metrics into five pillars:
| Metric pillar | Candidate metrics identified |
|---|---|
| Usage and activity | Total labels created; active shipping days; most active month; peak shipping day. |
| Financial value | Estimated savings; average savings per label; highest savings; total spend. |
| Operational efficiency | Most-used carrier; most-used service; void rate. |
| Reach and shipping patterns | Top destination; domestic and international shipping split; frequent shipping routes. |
| Reliability and trust | Non-voided labels; payment completion; refunds processed. |
I also prepared a structured designer-facing reference covering audience context, reporting period, metric categories, design intent, narrative flow, data considerations and explicit exclusions.
An important analytical constraint was recognising that not every proposed metric could be derived from the visible label table alone. Some required additional underlying data, and estimated savings depended on a defensible comparison price so the eventual experience would communicate credible value rather than unsupported figures.
Evaluating integration-led growth opportunities
ShipNLogic already supported an integration with Sage 3000. To support broader growth, the business wanted to evaluate another integration with an order management or business management platform used by businesses with substantial shipping needs.
The question was not simply which software was most popular, but whether an integration could create a viable channel to reach and acquire more shipping-intensive businesses. Platforms considered for investigation included Shopify, QuickBooks, Zoho Inventory, Linnworks, Oracle NetSuite and Ordoro.
I structured the research around seven evaluation criteria:
- —Adoption among manufacturing and e-commerce businesses.
- —Number and relevance of organisational users.
- —Market popularity and growth.
- —Availability and accessibility of APIs.
- —Ability to retrieve useful order information.
- —Integration feasibility.
- —Potential to identify and reach businesses using the platform.
The core product insight was that an integration should be evaluated by the commercial and customer acquisition opportunity it unlocks, not purely by the technical feasibility of connecting two systems.
Evaluating customer acquisition opportunities and business risks
Another growth initiative explored whether companies receiving shipments sent through ShipNLogic could be approached as prospective customers, on the assumption that shipment recipients might also have recurring shipping needs of their own.
I researched the legal and regulatory implications of this outreach concept across relevant jurisdictions, examining:
- —CAN-SPAM in the United States.
- —GDPR and ePrivacy rules in the European Union.
- —UK GDPR and PECR in the United Kingdom.
- —CASL in Canada.
- —The Spam Act in Australia.
- —LGPD in Brazil.
- —Japan’s Act on Specified Electronic Mail.
The assessment examined data collection, secondary use of recipient contact details, consent and lawful basis, sender identification, unsubscribe obligations and regional regulatory differences. Following this evaluation, the cold outreach approach was set aside in favour of pursuing lower-risk, product-aligned marketing opportunities.
Exploring alternative growth channels
Alongside setting aside recipient outreach, I contributed to mapping alternative ways ShipNLogic could leverage its product experience, customer relationships and software ecosystem to support acquisition:
| Opportunity | Strategic purpose |
|---|---|
| Branding on shipping labels | Increase product visibility |
| Customer savings reports | Demonstrate measurable financial value |
| Customer case studies | Build credibility and social proof |
| ERP and accounting partnerships | Reach businesses through existing software ecosystems |
| Logistics partnerships | Reach businesses with recurring shipping needs |
| Educational content | Position the platform around shipping cost optimisation |
| Referral programme | Encourage customer-led acquisition |
| In-app value communication | Reinforce value and encourage continued usage |
| Integration marketplace presence | Create additional discovery and acquisition channels |
Together, these options examined how ShipNLogic could broaden acquisition beyond outbound sales alone by connecting product value, partnerships and ecosystem discovery.
How I approached the work
Across these workstreams, my approach consistently traced product decisions beyond the immediate interface change to understand downstream effects on identity, workflows, data credibility and commercial growth:
- 01Understanding the business objective and the underlying customer problem.
- 02Examining the existing product experience and identifying limitations.
- 03Considering the implications of different product approaches.
- 04Evaluating user experience, operational and technical dependencies.
- 05Translating decisions into requirements and structured documentation.
- 06Collaborating with stakeholders, designers and developers.
- 07Considering the commercial implications and longer-term opportunities of product decisions.
An account upgrade affects identity, permissions and historical records; a status column shapes how users interpret operational reality; a customer value report depends on defensible calculations; and an integration shapes both engineering scope and acquisition reach.
What this experience demonstrates
ShipNLogic provided practical B2B SaaS product management experience across nine core areas:
- —Product thinking: Understanding the wider implications of individual product decisions.
- —Requirements engineering: Translating business problems into structured feature requirements and PRDs.
- —Account lifecycle management: Considering identity, permissions and data continuity.
- —Workflow analysis: Clarifying operational states and preventing ambiguous product behaviour.
- —Product analytics: Identifying meaningful metrics and translating them into customer-facing value.
- —Design collaboration: Preparing structured briefs and aligning data requirements with design objectives.
- —Market research: Evaluating software ecosystems and integration opportunities.
- —Commercial thinking: Connecting integrations, partnerships and product value to customer acquisition.
- —Risk assessment: Evaluating business initiatives against regulatory and operational constraints.
Reflection
ShipNLogic reinforced the importance of looking beyond the immediate feature request. A request to support another buyer type can uncover an account lifecycle problem; a new status column can reveal an underlying workflow modelling issue; a customer report can become a structured vehicle for communicating value; and an integration can be evaluated as an acquisition channel rather than just a technical link.
Effective product management connects those decisions to customer needs, operational realities and commercial objectives—strengthening my ability to analyse product problems, define clear requirements and evaluate how product work supports broader business growth.