feat(130): erli shipments and labels
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
# Database Schema
|
||||
|
||||
**Updated:** 2026-05-15 | **Total tables:** 63 | **Engine:** InnoDB | **Charset:** utf8mb4_unicode_ci
|
||||
**Updated:** 2026-05-16 | **Total tables:** 63 | **Engine:** InnoDB | **Charset:** utf8mb4_unicode_ci
|
||||
|
||||
---
|
||||
|
||||
@@ -385,6 +385,26 @@ UNIQUE: `(integration_id, shoppro_status_code)`
|
||||
|
||||
## Shipments & Delivery
|
||||
|
||||
**carrier_delivery_method_mappings** — Map marketplace delivery methods to local shipment providers
|
||||
| Column | Type | Nullable | Notes |
|
||||
|--------|------|----------|-------|
|
||||
| `id` | INT UNSIGNED | NO | PK |
|
||||
| `source_system` | VARCHAR(32) | NO | `allegro`, `shoppro`, `erli` |
|
||||
| `source_integration_id` | INT UNSIGNED | NO | `0` for global Allegro/Erli, shopPRO integration id for shopPRO |
|
||||
| `order_delivery_method` | VARCHAR(200) | NO | Delivery method label/code from imported order |
|
||||
| `source_service_id` | VARCHAR(128) | YES | Source delivery/shipping method id when available; used by Erli shipping dictionaries |
|
||||
| `source_vendor_code` | VARCHAR(64) | YES | Source carrier/vendor code; Erli uses this for `POST /shipping/external.vendor` |
|
||||
| `provider` | VARCHAR(50) | NO | Local shipment provider, e.g. `allegro_wza`, `inpost`, `apaczka` |
|
||||
| `provider_service_id` | VARCHAR(128) | NO | Local provider service id |
|
||||
| `provider_account_id` | VARCHAR(128) | YES | Provider account/credentials id when required |
|
||||
| `provider_carrier_id` | VARCHAR(128) | YES | Provider carrier code/id when required |
|
||||
| `provider_service_name` | VARCHAR(255) | YES | Display snapshot of provider service name |
|
||||
| `created_at` | DATETIME | NO | |
|
||||
| `updated_at` | DATETIME | NO | |
|
||||
|
||||
UNIQUE: `(source_system, source_integration_id, order_delivery_method)`.
|
||||
Phase 130 adds `source_service_id` and `source_vendor_code`; no new table is required for Erli delivery mappings.
|
||||
|
||||
**shipment_packages** — Prepared shipments with tracking
|
||||
| Column | Type | Nullable | Notes |
|
||||
|--------|------|----------|-------|
|
||||
@@ -414,7 +434,7 @@ UNIQUE: `(integration_id, shoppro_status_code)`
|
||||
| `sender_point_id` | VARCHAR(64) | YES | |
|
||||
| `reference_number` | VARCHAR(128) | YES | |
|
||||
| `error_message` | TEXT | YES | |
|
||||
| `payload_json` | JSON | YES | |
|
||||
| `payload_json` | JSON | YES | Provider request/response snapshot; Phase 130 may add `erli_external_parcel` after successful Erli external shipment registration |
|
||||
| `created_at` | DATETIME | NO | |
|
||||
| `updated_at` | DATETIME | NO | |
|
||||
|
||||
|
||||
Reference in New Issue
Block a user