Integration support

Many organisations use PartLogic as one system in a wider software supply chain—alongside ERP, WMS, finance, procurement, and custom applications. This page explains how we support teams building and operating those integrations, from self-serve documentation through assisted troubleshooting to dedicated programmes on Scale.

PartLogic acts as a data mastering and integration layer: we ingest product and inventory data from operational systems, govern and enrich records, and publish cleaner data back—without replacing your ERP or warehouse systems. For a deeper walkthrough of that model across WMS, ERP, and CMMS, see One portal, every system. Support is structured in a familiar UK B2B model: business-hours email, priority handling on higher tiers, and contractual service levels where agreed.

Who this covers

• In-house integration teams — developers, analysts, and IT owners connecting PartLogic to your stack.
• Operations and data teams — people responsible for catalogue quality, stock sync, and day-to-day integration health.
• Implementation and technology partners — consultancies and vendors deploying PartLogic for customers. For partnership models and enablement, contact us (programme enquiries, not the customer buying path).

Support by subscription

Integration support aligns with your PartLogic plan. See pricing for the full feature matrix.

Support channels

• Email — hello@partlogic.co.uk. Primary channel for integration questions, defect reports, and commercial escalations. We respond during UK business hours (Monday–Friday, 8:30–17:00 GMT), consistent with our contact page.
• Documentation — /docs including the API reference, portal API key guide, Zapier, Google Sheets, and data practices. Use these first for how-to and field-mapping questions.
• Slack — Available on Growth and above. We invite eligible accounts during onboarding or when you request access by email. Use Slack for quick coordination—not for posting API keys, passwords, or full production payloads. Escalate production-blocking issues (P1) via email; Scale customers should follow their agreed phone or escalation path.
• Contact form — /contact for sales, Scale programmes, and partnership introductions.
• Integrations portal — portal.partlogic.co.uk/integrations to create and manage API keys (not a support ticket channel).

Raising a good integration request

Clear requests help us reproduce issues and advise on fixes faster. Include as much of the following as you can:

• Environment (trial, staging, or production)
• Company or site name and your contact details
• Which integration path (API, Zapier, Google Sheets, Sage, custom)
• Endpoint or workflow step, with approximate time (UTC) of the failure
• Expected behaviour versus what actually happened
• HTTP status codes or error messages (never paste the full API key)
• Downstream system name and version (e.g. ERP or WMS product)
• Whether you have a workaround in place (helps us set severity)

Severity and escalation

We use a simple P1–P4 scale common in UK B2B support. Unless your contract states otherwise, response targets below are indicative and best-effort during UK business hours—not guaranteed service levels (those are agreed separately on Scale).

What we help with

In scope

• API authentication, stock endpoints, and published field behaviour
• Portal API keys, device setup, and expiry
• Documented connectors (Zapier, Google Sheets) and data import practices
• Trial and sandbox behaviour for integration testing
• Guidance on mapping PartLogic data to your ERP, WMS, or reporting tools

Typically out of scope for standard support

• Bespoke connector development (available via Scale or scoped professional services)
• Defects in third-party products (ERP, Zapier, network appliances)—we will help isolate whether the issue is on the PartLogic side
• Customer network, firewall, or VPN configuration on your infrastructure
• Guarantees that every channel or supplier system will sync without an agreed integration design

Working in your supply chain

Successful integrations depend on clear ownership on both sides. We recommend naming a technical owner and a business owner on your side, and aligning with owners of adjacent systems (ERP, WMS, finance) before go-live.

• Test first — Use a 14-day free trial or non-production environment to validate mappings and schedules before cutover.
• Change communication — Material API or behaviour changes are communicated via release notes and email to affected accounts. Plan regression checks in your deployment process when we announce updates.
• Data responsibility — You remain responsible for data entered or transformed in connected systems; PartLogic publishes governed records based on the feeds and rules you configure.

Partners

Implementation and technology partners receive the same technical documentation and trial sandboxes as customer teams, plus commercial alignment through our partnerships programme. Escalation to PartLogic solution engineers is available for joint customer work. Partner pricing and programme terms are agreed per partnership—contact us with subject line "Partnership introduction — [your company]".