Customer profiles now support a separate optional billing address, and invoice PDFs use that billing address automatically whenever it is fully filled. If the customer leaves it empty, the existing sender-address fallback continues unchanged.

JTL writeback now handles the customer's eBay orders whose real product row is stored as `nType = 0` instead of the `nType = 1` shape seen in the first batch.

JTL tracking writeback now handles the void-and-reprint path for JTL orders. If a previous outbound shipment for the same order was voided in Kenpost, a new printed label can replace that old JTL package tracking number and queue the current tracking for eBay.

This follow-up closes the missing bridge between JTL package writeback and JTL's eBay outbound queue. When a JTL order is an eBay order, Kenpost now writes the tracking number to JTL and also queues the shipment status for the next JTL-eazyAuction/eBay sync.

This follow-up tightens the new JTL tracking writeback so the package shipping method sent to JTL follows the Kenpost label product rather than blindly copying the order's older JTL shipping method.

This operational release adds JTL database tracking writeback to the normal label workflow. JTL shipments now create the matching delivery note, delivery-note positions and package tracking row directly in the customer JTL database, recalculate order delivery state, and surface the source-platform sync status on customer shipment screens.

This customer-facing release surfaces the completed bulk label creation UI polish in the latest version history: the selected-orders action, bulk review modal, localized labels, compact editable shipment rows and clearer confirm footer are now recorded together as the current customer-visible bulk label improvement.

This customer-facing release adds product SKU visibility directly onto generated DHL shipment labels. Labels created for marketplace orders now resolve SKU data from the platform order cache, print it under the tracking number in the existing label information block, and keep the line visually aligned with the original DHL typography while safely handling multiple or long SKU values.

This customer-facing follow-up refines the bulk label creation review one more step after the first cleanup: the missing label-product translation is now filled in, the review modal opens wider, selected shipments are displayed in a denser row layout with green operational accents, and the final action area now clearly shows how many shipments are ready before confirming bulk label creation.

This customer-facing release refreshes the bulk label creation surface on the orders page: the selected-orders action bar now shows proper localized copy instead of a raw translation key, the bulk label review dialog is wider and easier to scan, and each selected order is shown as a clean editable row so recipient details, address fields and label products no longer visually collide before labels are created.

This support release records the full invoice troubleshooting thread completed across the current conversation: the repository was audited locally before changes began, order and credit invoice PDFs were repaired so they no longer fall back to a generic `Customer` recipient when real buyer data exists, stale cached credit-invoice downloads were replaced with fresh render output plus safer storage-key versioning, and legacy zero-priced manual credit rows with active customer-specific pricing are now repaired in production while true free bonuses remain explicitly locked free.

This support release records the full Oznatır label-handoff thread completed across the current conversation: historical and same-day customer label allocations were verified directly in production, the requested label PDFs were exported locally outside the repo and packaged into ZIP archives, and those archives were then uploaded back through Kenpost's S3-backed label-inventory history flow so the customer could receive stable `app.kenpost.de/dl/...` links instead of one-time raw storage URLs.

This support release records the Amazon-focused work completed across the current conversation: Shopify-source Amazon orders were verified end to end, customer orders now show Amazon-facing identifiers and richer item metadata instead of Shopify-only values, the orders and shipments screens gained safer Amazon-specific filtering and relation fallbacks, and manual as well as automatic tracking handoff back to the Amazon source Shopify flow was repaired after live GraphQL and legacy-order matching issues surfaced during testing.

This support release records the full admin customer label-allocation thread completed across the current conversation: a live `1000` label allocation on the customer credits screen was traced to a transaction timeout during per-row `labelSource` updates, production checks confirmed that failed run did not leave partial customer assignments behind, and the allocation plus unassign flows were then hardened to use chunked bulk updates so large manual stock transfers no longer depend on one thousand individual record mutations inside the same transaction.

This support release records the full investigation and repair thread completed in the current conversation: Amazon orders coming through Shopify or Salestio now match stores more reliably during refresh, the `/admin/customers` page was rewritten to stop scanning unrelated customer relations across the whole dataset, and the later production follow-ups fixed the cursor and Gadget filter-depth failures that were still keeping the admin customer list intermittently empty after the first rollout.

This support release records the full customer-shipping thread completed in the current conversation: Amazon-source orders now use the real Shopify or Salestio sales time instead of the later sync timestamp, shipment regeneration now pauses behind an editable preflight dialog with locked product and weight rules, and the label sanitation layer was expanded so phone-like Amazon address contamination plus punctuation-heavy recipient or street input no longer degrade generated labels.

This release records the full Online Seller label-prefix thread completed in the current conversation: customer stores now have a dedicated setting that controls whether `Online Seller` appears on generated labels, that setting defaults to enabled for both existing and new stores so current operations keep working unchanged, and the later production follow-up closed the regenerate edge case for older shipment records that were still falling back to the old always-on behavior.

This support release records the full marketplace-tracking follow-up completed in the current conversation: a live eBay shipment that had already been sent on April 13, 2026 was manually repaired after label regeneration wrongly marked it as unsent, and the regenerate or resend tracking paths were then hardened so shipments that already completed source-platform sync are no longer sent again during later label regeneration attempts.

This release records the full admin customer-credits follow-up completed in the current conversation: the old single-product manual allocation flow was replaced with a bulk allocation table on the admin customer credits tab, the backend now accepts one batched admin allocation request for multiple label products at once, and the later support pass fixed both the weight-based product ordering and the missing admin permission that caused the new allocation flow to fail in production.

This release records the full customer-team-management thread completed in the current conversation: customer accounts can now add and manage internal team members from the customer portal, admin customer detail pages expose those team members directly for support visibility, and the later support passes hardened how sub-users inherit the main customer account's operational scope for orders, balances, sender-profile checks and related day-to-day shipping flows.

This support release records the full customer-orders follow-up completed in the current conversation: label credits now resolve to the correct products again after the sub-user regression, the orders list can filter down to only still-unshipped rows across supported store types, and the orders page no longer fires its first store request before the customer's accessible store scope has been validated.

This support release records the full customer-portal follow-up completed in the current conversation: team members now inherit the account owner's operational data where the portal should act on the shared company account, order detail loading was repaired across both customer and team-member sessions after multiple live failure paths were uncovered, customer-facing dates were aligned to European formatting, and team-member profile plus balance access was reduced to a safer read-only surface.

This support release records the full admin Amazon platform-detail follow-up completed in the current conversation: the `Platforms > Amazon` screen no longer treats Amazon account or store labels as if they were customer identities, the customer column now prefers real owner records with name and email, and the ownership resolver was hardened again after a live production check showed that some inactive or unsynced Amazon stores were still losing their customer link on the server-side data path.

This support release records the customer order-label follow-up completed after the video review in the current conversation: the orders create, regenerate and bulk preview flows now expose an optional company field, source order company names are carried into the review state when available, and recipient formatting now preserves `c/o` company delivery details through the existing label pipeline without weakening the shipment, credit or DE-only safety rules already in place.

This release records the full JTL database-mode follow-up completed after the original dual-mode JTL rollout. The direct SQL option now keeps saved database passwords non-readable after setup, the JTL order mapping was corrected against the real MSSQL schema so customer, address, item and status data no longer collapse in the orders list, and floating-point totals from JTL database imports are now rounded and displayed cleanly in the customer order table.

This support release records the full Amazon integration thread completed in the current conversation: production tracing first showed that Amazon bridge finalization could time out even after an authorization URL was created, so bridge requests were split into safer per-endpoint timeout windows. A later production screen recording then proved that `/customer/stores/amazon/new` was also crashing before the bridge flow even started, and the page was repaired by correcting the message-tree namespace that the customer Amazon route was reading during render.

This release records the admin customer-detail follow-up completed in the current thread: support teams can now see which store accounts a customer has connected directly from `/admin/customers/:id`, with a dedicated `Stores` tab that surfaces platform, store identifiers, sync footprint and connection timing without forcing a separate customer-side navigation hop.

This support release groups the full live follow-up completed across label generation failures, eBay refresh recovery, customer-side failed-manual-label cancellation and credit-invoice PDF corrections. Temporary storage-side failures that could leave labels half-generated are now handled more safely, customers can cancel and refund failed manual labels from the screens they actually use, and credit invoice PDFs now render the fixed service description and buyer block more reliably for both admin and customer downloads.

The customer support-mode exit path was corrected after a live production follow-up showed that returning from an impersonated customer account could still crash on `/customer` with a generic application error. The support-session restore logic is now centralized, production logs confirmed why the earlier route-action approach could lose the active support session, and the customer-side `Return to admin` control was moved back onto the authenticated Gadget action path so admins can leave customer mode reliably again.

Kenpost's marketplace coverage expanded again with full Kaufland and OpenCart onboarding inside the customer portal, but the work did not stop at simply adding two more store cards. During live rollout, access-control grants, customer-role repair paths, Germany-only Kaufland configuration, official platform branding and Kaufland sync behavior were all tightened so the new integrations behave more like first-class portal flows instead of fragile first releases.

JTL setup no longer depends on a single connection style. The customer store screen now offers a tabbed choice between the existing platform connector flow and a new IP-based SQL connection mode, so teams can keep the generated JTL connector path for licensed customers while also supporting direct JTL database reads for customers who prefer host-based access.

The JTL connector path was hardened across multiple Wawi test rounds so Kenpost now answers more of the connector handshake that JTL expects during setup. Authentication cookies, connector identity metadata, feature discovery, global data pulls and structured error payloads were all tightened to make platform-mode diagnostics far clearer when customer-side Wawi behavior differs across environments.

JTL setup inside the customer store area was reshaped from a rough connection form into a fuller managed workflow. Shared JTL status loading, test actions, refresh handling, disconnect behavior, import-range controls and clearer multilingual guidance were added so customers can manage JTL more like the other marketplace connections instead of treating it as a one-off experimental screen.

The customer profile page had become too stretched after the first security-method rollout, and the `Manage Security Methods` action could still feel unreliable because some customers were not actually reaching the dedicated security screen. The profile layout is now tighter again, email verification can be toggled directly from the profile summary, and the dedicated security page uses a cleaner standalone design with stronger direct navigation.

Label inventory handoff work no longer depends on customer login sessions alone. Admins can now export a customer's labels directly from the admin inventory area, while both admin and customer views now track whether labels were externally exported or externally used so teams can avoid re-downloading the wrong stock and can safely filter to labels that have not been handed off yet.

This release records the full translation sweep completed across the latest admin and customer pages. Missing page-level language trees were added into the central i18n structure, mixed hardcoded UI copy was moved out of route files, and the highest-risk operational screens now follow the shared release-and-translation pattern more consistently.

The profile redesign had improved the visuals, but the security-management entry point still felt unreliable because the `/customer/profile/security` screen was nested under the profile route in a way that could leave customers stuck on the same page. The profile layout is now tighter again, and sign-in protection management now opens in a true standalone security workspace while the profile page stays compact and easier to scan.

Purchase invoice PDFs now show the updated fixed service description requested for the invoice line item. The old wording and the appended label-product suffix were removed so these invoices present one consistent logistics-service description across the whole system.

Purchase invoice PDFs were improved again so the recipient section stays focused on the customer identity without exposing unnecessary e-mail details, and the single-line invoice layout no longer wastes space on a position column. Customer VAT information still appears automatically when it exists on the customer profile, but it is now omitted completely when it does not exist.

Customer-facing invoice PDFs could still feel anonymous in some purchase invoice flows because the buyer block sometimes collapsed down to a generic `Customer` label. Credit invoice buyer resolution is now relation-safe, the PDF layout now renders a clearer recipient section with the customer email, and the old five-day payment reminder was removed from the footer note area.

The sign-in email verification screen was still leaking raw GraphQL-style error text when a customer entered the wrong code. The screen now recognizes wrapped backend error codes as well, so customers see a normal invalid-code or expired-code message instead of an internal-looking technical error.

Support teams sometimes need to recover customer access when a user enabled sign-in email verification on the wrong mailbox or can no longer receive verification emails. Admins can now disable customer email two-factor directly from the customer detail page, and the rescue flow clears any pending sign-in verification codes so the customer can immediately fall back to normal email-and-password sign-in.

Customers could reach the email verification step after entering the correct password, but both code verification and resending a code were failing with a raw `GGT_PERMISSION_DENIED` message. The unauthenticated permission chain for those auth actions is now restored, and the sign-in and email verification screens now translate raw backend failures into clearer customer-facing messages instead of exposing internal Gadget errors.

The customer profile redesign looked cleaner, but in production the `Manage Security Methods` action still felt broken and customers could not reliably reach the dedicated security page to disable email verification. The profile screen now includes a live inline email verification toggle and uses a browser-native security link, while the overall right-hand layout was tightened so the page feels more professional without excessive vertical drift.

The profile redesign introduced a clearer dedicated security area, but the main profile CTA still was not opening that screen reliably in production. Security management actions now use an explicit page transition so customers can always reach the dedicated sign-in protection screen and manage email verification without the click silently doing nothing.

The customer profile page was rebalanced again after the first security redesign still felt too tall and visually awkward in production. The profile screen now keeps a tighter account overview with clearer actions, while sign-in protection methods live in a more distinct dedicated security page where email verification can be managed cleanly and future SMS/app methods are presented as roadmap cards instead of stretching the main profile layout.

The customer profile page became too tall and visually heavy after the new multi-method sign-in protection UI was added directly into the main profile layout. Security management now lives in its own dedicated screen, while the profile page keeps only a compact summary and a clear entry point to manage sign-in methods. The customer orders table was also adjusted so store names no longer appear empty when the source store label is missing in row data.

The sign-in outage was caused by the email two-factor flow writing a custom pending-user field into the Gadget session payload, which the live session schema no longer accepted. Sign-in now carries pending two-factor state through a signed challenge token instead of mutating the session with unsupported fields, so normal customer logins work again and optional email two-factor continues to function.

The admin carrier log sheet was reshaped into a clearer operational timeline so support teams can see when a tracking query ran, when it finished and what result came back without digging through raw S3 file names first. The latest detected outcome now stays visible at the top, matched runs read like a query history, and raw JSON remains available only as a secondary debugging view.

Admin platform detail pages now recover customer identity more reliably when a store row arrives without a hydrated `user` relation. The analytics job now uses the store's `userId` to look up the owning customer account, includes first and last name fields in its display-name logic, and falls back to the account/store name only when a customer record still cannot be reconstructed.

Customer accounts can now enable an optional email-based two-factor step from the profile page. When enabled, password sign-in pauses until the user enters a fresh 6-digit code delivered by email, and admin customer detail pages now surface whether that protection is active.

The language sweep moved the most recently added admin and customer setup screens out of scattered in-file locale blocks and into shared translation files. Platform analytics, admin settings pages, the carrier log sheet and several customer store-connection flows now resolve their UI copy through the central i18n layer, making later translation maintenance much safer.

The admin Platforms overview now handles the Manual card differently from marketplace stores: instead of looking for explicit store connections, it treats every customer account as having a default manual label account. Manual usage therefore reflects all customer accounts, while manual order and label totals are derived from real `sourcePlatform=manual` orders and the labels created from those manual shipments.

The platform analytics follow-up now fixes the last misleading metric on the detail pages: label totals no longer stay at zero just because the analytics job relied too heavily on bare relation IDs. The calculation now resolves store ownership through shipment, order and label-source links together, so marketplace detail screens reflect real label usage alongside the already-correct synced order counts.

The earlier admin Platforms rollout was repaired again after production still showed permission errors and zero values on some accounts. Platform analytics now load through a dedicated authenticated REST endpoint instead of the blocked route-loader path, while the carrier log viewer was widened, made scroll-safe, and upgraded to show the newest worker result summary before the full timeline.

The new admin Platforms analytics screen was repaired after the first rollout surfaced two production issues: the browser-side analytics request hit a `GGT_PERMISSION_DENIED` wall and the direct per-platform route did not resolve reliably. The page now loads its analytics on the server, the detail drilldown opens correctly, and the release history records the repaired rollout as its own version.

The admin label-check log viewer was corrected so labels with existing per-tracking S3 JSON logs no longer appear empty just because the worker stored them under a flat `tracking/logs/<tracking>.json` key or because the runtime resolved S3 credentials through config-backed storage settings.

The admin Platforms screen was upgraded from a static availability toggle page into a real marketplace analytics view. Admins can now see how many stores are connected per platform, how many orders were synced, how many labels were created, which platform is used most, and can open a dedicated detail screen listing the customers and accounts behind those numbers.

The admin customer-pricing workflow was tightened in the same support pass: label products now appear in stable base-price order on both pricing entry points, customer IDs remain visible for support work, and the left-hand customer selector was redesigned so the added identity metadata no longer feels cramped.

A fresh localization sweep connected many more admin and customer screens to locale-aware copy, including operational tables, dialogs, filters, onboarding surfaces and profile flows that still showed hardcoded English. The shared language switcher was also simplified by removing its redundant static label, keeping the header cleaner while EN, TR and DE switching behavior stays the same.

Invoice generation was corrected so the billed customer is now clearly identified from the customer profile instead of falling back to incomplete order-recipient data. Customers and admins can now save an optional tax or VAT identifier on the customer profile, and invoices print that value automatically whenever it exists.

Admin label inventory visibility was expanded across both Dashboard and Label Products so teams can switch between all, available, allocatable, assigned, consumed, void and check-error counts without losing count accuracy. The product table now exposes the raw status totals explicitly, the zero-count regression caused by relation-shaped product ids was fixed, and both admin screens were tightened visually so the inventory area no longer pushes the main content too far down the page.

Legacy customer label purchases no longer get stuck with blank product names or zero-valued credit invoices after customer-specific pricing is entered later. Historical repricing now runs automatically from the pricing save flow, admin and customer purchase views read safer product fallbacks, and generated credit-invoice PDFs now identify the purchased label product explicitly.

The platform was cleaned up after a broader system audit: mixed-language customer and admin screens were pushed back toward an English-first baseline, and stale purchase snapshots no longer override the real product and pricing information derived from linked label sources.

Admin label checks now expose the per-label S3 JSON log history directly inside the UI, so operators can inspect the exact carrier-query timeline for a label without leaving Kenpost.

Manual single-label checks no longer bypass the S3 workflow. The label-check screen now writes one-label JSON requests to S3, shows a live progress popup and displays the returned result in place when the fast background worker finishes.

Label-check exports can now be generated automatically every six hours for the three main inventory states, reducing the need for repeated manual bulk queueing and keeping S3-backed result files continuously refreshed.

Carrier rechecks for labels that Kenpost has already consumed are now treated as informational status updates instead of faulty or void candidates, which prevents false negative inventory transitions while still exposing transit or delivery visibility.

Customer credit allocation and label purchasing now consume stock from the oldest eligible labels first and permanently exclude unusable inventory such as void labels or labels with carrier check errors.

The admin customer detail Overview tab was redesigned to reduce dead space, rebalance the content grid and make the account summary, recovery actions and sender details feel like one coherent operational dashboard.

Admin customer detail tabs now stay on the currently selected section after a page refresh, making deep customer support work faster and easier to share through direct links.

The admin customers index now exposes the internal customer ID directly in the listing, helping support and operations teams jump to the correct account faster when an ID is referenced in logs, invoices or customer detail URLs.

The main customer-pricing screen no longer forces operators to work through a single dropdown. It now provides a searchable customer list and a focused editing workspace for the selected account.

Tracking-number links now open in a new browser tab consistently across the Kenpost interface, preventing operators from losing their current context every time they inspect a shipment or label.

The customer portal received a broader visual refresh: the dashboard now presents a richer, more colorful operational summary, and the orders page no longer lets long store or label names collide inside the filter controls.

Customer accounts can now store an optional mobile phone number from registration onward, while keeping the existing signup and profile flows backward-compatible for older accounts.

A broader permission audit was added to reduce `GGT_PERMISSION_DENIED` failures, and the missing admin grants uncovered during that audit were wired into the access-control layer before release.

The admin customer-detail workflow received a set of quality-of-life upgrades, including a more usable overview of pricing-related work and supporting navigation improvements that make customer management faster during support sessions.

This release consolidates the full support work completed across the current conversation: admin label checks now support customer-based filtering and full filtered S3 queueing, the carrier-check history popup shows request IDs and stays in sync while pending runs remain active, background polling stops automatically when there is nothing left to check, and the Missing Labels page can export customer-free PDF reports for problematic labels.

This release collects the full support work completed across the current conversation: admin customer pricing now loads, saves and reopens correctly from both the bulk pricing page and the customer detail screen, customer manual label creation gained clearer reset and corporate-recipient handling, and customer credit invoices or balance history now recover missing product and pricing context while the generated PDF invoices follow the new naming, VAT and numbering rules.

This release captures the full thread of work completed in the current conversation: the legacy Track123 and whereParcel carrier-check paths were removed from the active label-check flow in favor of the S3-based label usage check, admin customer email verification now stays reflected after refresh, newly created customers with incomplete sender profiles are automatically redirected to finish their company address before creating labels while older customers remain grandfathered, and the customer orders page now reliably recognizes created shipments so label downloads and regenerate actions stay visible after creation.

This release captures the integration work completed during the current thread: Shopify stores now have a dedicated connection test so customers can verify their token before waiting for the next sync, eBay tracking write-back now keeps shipment-level sync state with default-on behavior and manual resend controls, and OTTO order sync was pulled in-house so Kenpost now fetches, compresses and stores the cache directly in S3 instead of posting to the legacy Cloudflare worker.

This release replaces Kenpost's earlier direct Amazon connection path with the new Salestio bridge workflow, hardens the customer-facing Amazon authorization experience with timed confirmation, modal guidance and safer operational masking, adds a separate Shopify source pipeline for Amazon orders written into the shared gzip-backed cache flow, propagates Amazon disconnect and delete actions back to the bridge server, and repairs the admin customers page so customer and credit management can load again without cursor-pagination failures.

This release groups the customer-account support work completed in the current thread: admins can now manually recover blocked customer access by verifying emails and setting temporary passwords, the customer buy-labels page still enforces stock limits without exposing live stock counts, the admin customer invoice tab now respects Gadget's page-size limit, customer credit summaries were rebuilt to handle both `labelBalance` rows and legacy assigned-label records correctly, and obsolete onboarding warnings were removed from customer management screens.

This release brings customer-side shipment cancellation much closer to admin-grade recovery: customers can now cancel and refund eligible shipments from their own shipments page, legacy rows with incomplete ownership data are handled more safely, orphaned shipment records can reconstruct their missing label link from stored shipment artifacts, and refunded or void rows now present clearer visual states without misleading restore actions.

This release brings WooCommerce store management much closer to the production-ready eBay experience: the Woo connect page now doubles as a live connection workspace with masked key visibility, API health diagnostics, reconnect and disconnect controls, store-specific management routing and clearer guidance when a Woo site is reachable but still misconfigured for public REST access.

This release removes WooCommerce's dependency on the missing external sync worker path that was returning `404`, moves Woo order imports onto the same internal S3-backed cache pattern used by the other marketplaces, and corrects the legacy REST URL construction so Kenpost can distinguish true Woo auth failures from malformed route probing.

This release captures the final eBay order-shipping follow-up: Kenpost now preserves the best available street data during eBay cache refreshes, automatically opens a manual address-completion flow when older eBay orders are missing street information, and avoids secondary shipment failures caused by treating an eBay username like a valid email address.

This follow-up release hardens the dedicated `Canceled Labels` admin screen after production still showed an empty error state: the page now reconstructs canceled-label rows directly from shipment, label-source, order, purchase and user model reads in the browser, so voided shipment history remains visible even if the older action path fails or returns an unexpected wrapper.

This release finishes the admin shipment cancel follow-up by separating archived cancel records from the live `/admin/shipments` workspace, repairing the dedicated `Canceled Labels` loader so voided shipments reliably appear in their own review screen, and tightening the archive behavior so support is no longer distracted by stale cancel tombstones among active labels.

This release records the dashboard follow-up completed after the refreshed admin overview still showed `Unknown`, `Unlinked` and misleading zero-state values: `/admin` now resolves customer, order and label-product context through nested purchase, shipment, store and label-source relations instead of depending only on sparse direct ids, inventory widgets describe true stock availability more honestly, and the overview layout was tightened so operators can trust the snapshot more quickly.

This release follows up on the shipment cancel and return recovery work with clearer admin wording: `/admin/shipments` now distinguishes canceled shipments from faulty labels, shows whether the linked label sits in customer stock or Kenpost stock, disables redundant recovery buttons once a label is already in the intended place, and adds a direct shortcut to the dedicated `Canceled Labels` workspace.

This release adds a clearer customer-facing explanation for the older eBay order cases discovered during live label testing: when an eBay order older than 90 days opens the manual address-completion dialog because the street line is missing, the popup now explains that eBay may no longer return full street data through the API and that the missing address must be completed manually before label creation can continue.

This release records the follow-up shipment recovery fix completed after fresh production failures on `/admin/shipments`: cancel and return flows now recover customer ownership through the order's store owner when direct shipment or order links are blank, legacy DHL `1 kg` labels no longer fail product inference on overlapping weight boundaries, and admins now have a dedicated `Canceled Labels` screen under `Labels` to review voided shipments and see where each linked label ended up.

This release records the end-to-end eBay integration completed and live-tested in the current support thread: customers can now connect eBay stores through Kenpost's own OAuth application without entering app keys, eBay order imports now run internally and persist to the same S3-backed order cache used by other marketplaces, the customer order screen gained eBay-specific sync ranges and clearer reconnect or disconnect controls, and follow-up production fixes hardened store deletion, session handling, address recovery and label creation for older eBay orders where the marketplace suppresses street-level PII after 90 days.

This release records the support-thread fixes completed after live shipment and admin customer investigations: transient internal label generation failures are now retried automatically instead of failing immediately on the first temporary storage error, the admin shipments page no longer disguises real failed labels as `Preparing`, and admin customer listing/detail screens now show more complete counts while the customer list page expands from 25 to 250 rows.

This release captures the label-management and customer-account fixes completed in the current support thread: admins can now allocate up to 1000 labels in one operation without hitting the earlier 250-query ceiling, customer detail and admin inventory views now resolve assigned product and owner information more reliably even when Gadget relations arrive as raw ids, new customer accounts regain the missing access needed for the portal, and single label downloads from the customer inventory now download directly instead of opening as an inline PDF preview.

This release records the follow-up hardening completed after real-world 995-label export tests: the customer inventory ZIP worker no longer silently restarts the same archive job during finalization, the export runtime window was expanded substantially, automatic queue retry for the same job was disabled, and history entries now surface the later upload phase more clearly.

This release captures the latest customer label inventory export hardening completed in the current support thread: large ZIP exports were moved out of the direct request path into a background queue, the archive worker was given a longer execution window, PDF collection throughput was increased, and the customer portal now surfaces queued, running and downloading progress states while the archive is being prepared.

This release collects the admin label-operations work completed in the current conversation: label inventory and label checks gained upload-date filtering, admin inventory pagination was expanded to 500 and 1000 rows per page, and background carrier-check batches now persist a full history with manifest-backed summaries and downloadable reports.

This release consolidates the full customer label inventory thread completed across the current conversation: the customer portal gained a new `Label Inventory` section under `Shipments`, customers can now view only their assigned labels in an admin-inspired inventory screen, bulk ZIP export was added and expanded to 1000 labels with stronger storage fallbacks, and follow-up UI cleanup removed wasted space and redundant inventory summary content.

This release records the full customer inventory thread completed in the current conversation: a new `Label Inventory` workspace was added to the customer portal, assigned labels gained customer-scoped ZIP export and secured download handling, the export limit was raised to 1000 labels with stronger S3 and proxy fallbacks, and the customer shipment or inventory layouts were tightened to remove wasted space and redundant summary cards.

This release records the full shipment support thread completed in the current conversation: old cancel and return flows were hardened for legacy label rows, admin shipment statistics were repaired end to end, oversized shipment pagination errors were removed from customer order screens, and `Return To Stock` gained a final metadata-based label-product fallback so older shipments can be recovered even after direct product links were lost.

This release captures the full label-audit support thread completed in the current conversation: DHL carrier verification was migrated onto the external tracking proxy for direct checks, label auditing was split out from stock inventory into its own `Label Checks` workspace, bulk verification moved to an S3 query/result exchange with background polling, and the resulting carrier data now drives clearer open, confirmed-used, faulty and auto-void decisions for reusable labels.

This admin release captures the full workspace improvements completed in the current conversation: `/admin/shipments` now shows dynamic label-generation totals for today, yesterday and rolling 7, 30 and 365 day windows, while the crowded left navigation was reorganized into cleaner collapsible Labels and Billing sections without changing the underlying admin pages.

This support release captures the full customer label thread completed in the current session: bulk ZIP packages were revalidated around the combined PDF, broken printable labels were repaired for Acrobat, bulk ZIP history gained true regenerate support and customer PNG or JPEG downloads returned as on-demand conversions without slowing normal PDF generation.

Admin invoices were expanded into a true cross-customer workspace with order and credit invoice visibility, manual invoice creation and editing, editable credit invoice values, corrected label-credit pricing and a PDF template refresh aligned to the Makpirtuk reference invoice.

Customer-facing label delivery was reworked so newly created, regenerated and previously stored shipment PDFs are printable again, while manual and store bulk downloads now arrive in a more recoverable single-ZIP format with combined and ordered label files.

Admin shipment operations were hardened around customer-style label downloads, explicit cancel versus return stock behavior and automatic recovery when PNG or JPEG artifacts are missing or stale.

An end-to-end investigation of intermittent admin label upload complaints distinguished successful backend uploads from client-side error reports, confirmed hardcoded Turkish copy in the upload UI and separated that from browser-translated root error-boundary text.

Admin purchases now stay centered on Shopify order reconciliation instead of per-product mapping, with clearer sync outcomes and a page-open auto-sync loop for recent billing orders.

Shopify billing repair was reframed around order metadata and existing purchase reconciliation so backfills no longer depend on Shopify product mapping and sync results explain what was actually refreshed.

Internal shipment downloads, regenerate flows and DHL label address rendering were tightened so regenerated labels resolve the right artifact set and long German street lines fit more reliably.

Manual shipment downloads were hardened again around production font serving, customer-side PNG or JPEG preparation and safer regenerate follow-up behavior.

Manual and internal shipment flows were hardened around stuck labels, regenerate recovery, customer shipment visibility and safer artifact delivery.

Carrier checks, purchase reconciliation and admin recovery tooling were realigned around DHL production tracking and safer back-office repair flows.

Root-level request handling and the manual label workspace were hardened so stray submits no longer crash the app shell.

Store-order fulfillment, bulk label creation and admin recovery tooling were aligned around the internal label engine and safer operational controls.

Manual labels now render fully inside Kenpost, store multiple artifacts in S3 and can be reviewed directly from the create-label screen.

Carrier checks, Shopify billing recovery and customer administration were tightened to fail safer and recover missed flows more reliably.

Label inventory, Shopify billing, internal PDF uploads and version tracking were hardened in one release.

Operational control screens around label sources were consolidated and made safer for support use.

Shopify-paid orders can now be recovered even if the webhook flow is missed.

Admin purchases was upgraded from a raw table into an operations workspace.

Shipment list quality was improved with stronger fallbacks for order, recipient and product data.

Shopify order sync was moved into the app while keeping S3 order cache compatibility.

Label buying and customer balances were aligned with real inventory assignment.

Shipment creation and regeneration flows were made more defensive.

Platform-specific order detail pages were expanded across the supported marketplaces.

Customer detail became the main operational cockpit for label credits and history.

Invoice generation, numbering and downloadable PDFs became a first-class flow.

Referral and commission features were added around invoice activity.

Label products, stock counts and customer-specific pricing became manageable from admin.

Marketplace onboarding routes and credential handling expanded across the supported platforms.

The customer portal matured into a real daily workspace for stores, orders, shipments and invoices.

Admin navigation and operational areas were formalized into a central command center layout.

Authentication, sign-up, sign-in and onboarding flows were established.

The initial app structure, route shells and domain areas were laid down.