Skip to content
Database ⇄ ERP

Google Cloud Spanner to Körber WMS integration — real-time, two-way sync

Keep Google Cloud Spanner and Körber WMS in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from Mulesoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Google Cloud Spanner and Körber WMS

Give your engineers Körber WMS's data in Google Cloud Spanner: read it with normal queries, write back through the sync, and skip the ERP API entirely.

ERP data sits behind interfaces built for the ERP's own modules, not for your internal systems. Teams that need those records, for reporting services, internal tools, or automations, end up writing integration code against a strict API and maintaining it through every upgrade.

Stacksync mirrors Shipments, Locations, Tasks, Returns from Körber WMS into Google Cloud Spanner and keeps both sides consistent in real time. Whatever Körber WMS is the system of record for, whether financials, operations, people, or procurement, those records become rows your code can query, and changes written in Google Cloud Spanner sync back into Körber WMS with its validations respected.

Common use cases

  • Use change streams to feed near-real-time copies of operational tables into an analytics warehouse.
  • Run a two-way sync between Spanner and a SaaS tool so edits made by ops teams land back in the application database.
  • Sync inventory positions from Körber WMS to an OMS or e-commerce platform so sellable stock reflects the warehouse
  • Push orders from the ERP into the WMS for fulfillment and return shipment confirmations automatically

Where Körber WMS is the HR system of record: people data for internal systems

Worker and org records stay current in Google Cloud Spanner for provisioning, access, and reporting systems that read from the database.

Controlled write-back

Choose exactly which tables and fields may flow from Google Cloud Spanner back into Körber WMS, keeping the ERP authoritative.

Read ERP records with a query

Records from Körber WMS live in Google Cloud Spanner as ordinary tables or collections, joinable with the rest of your data.

What you can sync between Google Cloud Spanner and Körber WMS

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Google Cloud Spanner objects Körber WMS objects
Views Read-only projections useful for shaping data before it leaves Spanner. Locations Bin and zone definitions scope inventory data during mapping.
Databases Top-level containers that scope schema and sync configuration. Tasks Warehouse task data supports labor and throughput reporting.
Tables Relational tables mapped one-to-one to sync targets. Returns Return receipts flow back to commerce and ERP systems for refunds and restocking.
Rows The unit of read and write in each sync cycle, keyed by primary key. Items Item definitions keep the WMS aligned with the ERP item master.
Interleaved tables Child rows physically co-located with parents; synced as related records. Inventory On-hand quantities by location feed availability in order-taking systems.
Secondary indexes Used to make incremental read queries efficient on non-key columns. Receipts / ASNs Inbound notices and receipt confirmations sync with procurement systems.
What ships with Google Cloud Spanner ⇄ Körber WMS

Connect Google Cloud Spanner and Körber WMS for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Google Cloud Spanner–Körber WMS connection.

Real-time

Two-way sync

Changes in Google Cloud Spanner or Körber WMS instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Google Cloud Spanner or Körber WMS data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Google Cloud Spanner or Körber WMS record.

Observability

Monitoring

Track your Google Cloud Spanner ⇄ Körber WMS sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Google Cloud Spanner and Körber WMS.

How the Google Cloud Spanner and Körber WMS connectors work

Google Cloud Spanner

Integration surface
gRPC/REST client API with SQL query surface (GoogleSQL and PostgreSQL-interface dialects)
Authentication
Google Cloud IAM (service accounts)
Change detection
Change streams (log-style CDC), or timestamp-based polling queries
Capabilities
read · write · CDC
Rate limits
Throughput is bounded by the instance's provisioned compute capacity rather than a fixed API quota.

Körber WMS

Integration surface
Varies by deployment; typically host-interface messages, file exchange, or vendor APIs via middleware
Authentication
Credentials issued per deployment
Change detection
Polling or message/file-based export from the WMS host interface
Capabilities
read · write
Rate limits
Constrained by deployment architecture rather than published API rate limits
How it works

How to connect Google Cloud Spanner to Körber WMS — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Google Cloud Spanner and Körber WMS with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Google Cloud Spanner connected
    Körber WMS connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Google Cloud Spanner and Körber WMS objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Google Cloud Spanner ⇄ Körber WMS
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Google Cloud Spanner Körber WMS
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Google Cloud Spanner and Körber WMS integration FAQ

SECURITY

Security teams love Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

SOC 2 type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Related integrations

Every pair below is a real-time, two-way sync. Search all 386 integrations available for Google Cloud Spanner and Körber WMS.

Popular · 8 of 386
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.