SKU Studio — Create & Map Internal SKUs

Connection

The connection string is stored securely as a server secret named DATABASE_URL. To change it, update the secret in project settings.

DATABASE_URL configured

Connection successful

Tables seeded (sku_mappings)

Nothing to migrate yet

Your browser has no locally saved mappings in this profile. This usually happens when:

You haven't created any mappings yet.
Mappings were created while the database was already connected — they went straight to Postgres.
You're on a different browser, profile, or incognito window than where the mappings were made.

Create a mapping

Set DATABASE_URL in the project's secret settings. Example: postgres://user:pass@host:5432/dbname. Your database must accept connections from Lovable's servers (public host + SSL recommended).

Connectivity diagnostics

Runs a step-by-step check: parses the connection string, tests raw TCP reachability to host/port, then attempts a Postgres handshake with and without SSL. The exact failure reason for each step is shown below.

Schema

The seed step creates a single table used by SKU Studio.

CREATE TABLE IF NOT EXISTS sku_mappings (
  id UUID PRIMARY KEY,
  internal_sku TEXT NOT NULL,
  product_name TEXT NOT NULL DEFAULT '',
  type TEXT NOT NULL CHECK (type IN ('internal','external')),
  portal TEXT NOT NULL,
  marketplace_sku TEXT NOT NULL,
  status TEXT NOT NULL DEFAULT 'Active'
    CHECK (status IN ('Active','Inactive')),
  created_at TIMESTAMPTZ NOT NULL DEFAULT NOW()
);