Warehouse platform & integrations · Earlier employment / team work
Warehousing & systems integration
Over several years at BrandLink, I worked across a comprehensive warehousing system and its integrations: receiving, inventory, orders, fulfilment, client portals, print production, freight and ERP.
- My role
- Full Stack .NET Developer — work delivered through BrandLink
- Project status
- Historical delivered work
The task
A warehouse serves many clients, products and ordering channels. Goods receipts, stock balances, allocation, packing, freight and dispatch have to stay connected to client records and external systems. Staff need usable operating tools, while clients and customers need accurate order and shipment information.
My contribution
I worked across all parts of the BrandLink warehousing system over several years, including backend processing, client and administration workflows, data and external integrations. My work also covered the connected print-production pipeline and personalised commerce. Running the attached print facility gave me direct experience of the operational work the software supported.
What people can do
Receiving and inventory
Inward deliveries record expected and received goods, with lot, batch and expiry information where required. Warehouse and virtual-warehouse stock, product movements and units of measure support inventory and order processing.
Orders and stock allocation
Orders from multiple client channels map into warehouse records, product references and stock allocation. Processing accounts for different units and packaging, records stock movements and batches eligible orders for fulfilment.
Packing and freight costs
Shipment packaging, dimensions and weight feed freight quotes. Rate cards calculate pick-and-pack charges for units, bundles, cartons and pallets, alongside packaging and order-establishment costs.
Dispatch and shipment visibility
Warehouse shipment events return carrier, booking and tracking information to the originating client system. Platform-specific callbacks update fulfilment, including customer-notification requests on Shopify.
Commercial and ERP integration
Integration points span Shopify, BigCommerce, eBay and Salesforce, CargoWise warehouse exchanges, freight services and Dynamics NAV. REST, XML and SOAP mappings connect orders, inward deliveries, stock and status updates.
Client and brand administration
MyBrand portal work supports tenant-specific catalogues, media, products, suppliers, departments, cost centres and purchase orders. Branded client access and administration sit alongside the warehouse and integration workflows.
Print and personalised products
Connected workflows include live product artwork, saved proofs and order-driven production files for personalised tins, plus PrintIQ quoting, PDF preparation and print batches across the wider print operation.
Reconciliation and operating tools
Background jobs, retained message references, correlated logs and exception alerts help staff follow processing. Stock comparisons produce variance reports and configured storefront inventory updates.
How the system works · diagram
Warehouse operations
- Inward delivery
Record incoming goods and receipt information.
- Stock + lots
Maintain warehouse stock, movements and batch references.
- Allocate orders
Map products, quantities and warehouse allocation.
- Pack + freight
Calculate packaging, fulfilment charges and freight.
- Dispatch
Ship goods and retain carrier and tracking references.
Connected order and shipment flow
- Client channels
Receive orders from commerce and business systems.
- Map + queue
Translate each client’s data and schedule processing.
- Warehouse jobs
Create warehouse records and hand off fulfilment work.
- Shipment events
Receive dispatch, carrier and tracking information.
- Client updates
Return status to source systems and customer-facing orders.
Warehouse operations
My work at BrandLink spanned the warehousing system over several years. That meant working with the records and interfaces people used to receive goods, manage inventory, process orders and arrange fulfilment, as well as the integrations around those tasks.
Warehouse workflows included inward deliveries with lot and expiry records, physical and virtual warehouses, product movements, allocation and units of measure. Order processing adds packaging, pick-and-pack charges and freight, while receipt information and shipment status feed connected client and ERP systems.
System integrations
Commerce and business integrations included Shopify, BigCommerce, eBay and Salesforce, alongside CargoWise, freight services and Dynamics NAV. Each channel needed its own authentication, product and order mappings, processing jobs and return-status handling. XML/SOAP ERP exchanges covered inward-delivery receipt data as well as commercial orders.
Client-facing and administration work included MyBrand’s tenant-specific brand catalogues, media, merchandise and organisational records. Stock reconciliation, variance reporting and operational alerts helped connect what the warehouse held, what client systems displayed and what staff needed to resolve.
Personalised products and print
The Nestlé Milo personalised-tin workflow is one example of this wider work. A shopper edits artwork in an embedded Customer’s Canvas editor, with saved proofs and a return-to-edit link in Shopify. Order ingestion extracts personalisation, selects a production template and generates high-resolution artwork linked to the order and SKU. The physical process continues through printing, application to the tin, packing and shipment tracking back to the client store and customer.
Across the print operation, I also integrated PrintIQ and built the receiving production pipeline, including PDF checks, pagination, slip sheets and batches. Running the attached print facility helped me connect software decisions with production, finishing and despatch. Other brand storefront work included Victoria Bitter and Carlton campaigns.
Managing handoffs across operational systems
Constraint
Warehouse stock, client orders, print jobs, carrier bookings and ERP records have different lifecycles and identifiers. Staff need to follow the same work across those boundaries and see when a handoff needs attention.
Approach
Map channel data into warehouse records, retain external references and product movements, and use background processing for integration work. Return receipt and shipment information to the originating systems, with reconciliation and alerts around exceptions.
Trade-off
Each client and external platform brings mapping and support requirements. Keeping those adapters and operational states explicit creates ongoing maintenance work, but gives staff a way to locate and resolve incomplete processing.
Connected business operations
- Inward deliveries, lot/batch references, warehouse inventory, product movements and units of measure.
- Multi-channel order processing, stock allocation and eligible fulfilment batching.
- Packaging, rate-card pick-and-pack costing, freight quotes and dispatch handoffs.
- Client and ERP exchanges for receipt, order, inventory and shipment information.
- Tenant-specific client catalogues, media and merchandise administration.
- Stock reconciliation, variance reports, background jobs and operational alerts.
- Connected artwork generation, PrintIQ quoting and print-production preparation.
Technical context
C#/.NET, SQL Server, Entity Framework and Hangfire, with REST, XML and WCF/SOAP adapters across client, warehouse, freight and Dynamics NAV systems. MyBrand used host-resolved tenancy, scoped queries and tenant-specific Azure Blob media storage. Connected print and commerce work used MediatR, PDF processing, PrintIQ, JavaScript, Shopify Liquid and Customer’s Canvas APIs.