Post Label Center (PLC) Manager for WooCommerce

By Sunlime Web Innovations GmbH

★ 5.0/5 (4 ratings)10+ active installationsVersion 1.4.0

This plugin extends WooCommerce and allows exporting orders to the PLC-portal of the Austrian Post.

Description

This plugin extends the basic WooCommerce features and adds a support for the PLC-Portal of Austrain Post. If an order is ready for delivery and the status is changed to PLC all data is submitted to the PLC manager.

The communication is done through a SOAP interface automatically and therefore no import export is required.

Optional Shiptastic synchronization can be enabled on the PLC Options page when Shiptastic is active. Each confirmed PLC parcel becomes one Shiptastic shipment with its allocated items, weight, dimensions and Austrian Post tracking number. PLC determines service selection and parcel packing. Both synchronization and marking shipments as shipped are disabled by default. Upgrading does not automatically enable Shiptastic synchronization or shipment status changes.

Before an export starts, refunded item quantities are deducted from the ordered quantities. Amount-only refunds do not change quantities. Declared goods values use the discounted order line amount including VAT, divided by the original ordered quantity, in the order currency. Customs fields resolve independently from variation, parent product and settings defaults.

Products require a positive weight and must not individually exceed 31.5 kg. Zero-quantity, fully refunded and virtual items are skipped. Packing preserves order-item order and uses integer weight calculations to avoid unnecessary parcels at the weight boundary. Missing or invalid weights, quantities, service codes and populated customs fields stop the export with an order note before any shipment request.

Developers can opt into exclusive two-unit parcels for explicitly selected products with the splc_packing_rules filter. No rules are enabled by default. Each complete pair occupies its own parcel, with no other products added. An odd remaining unit is packed with the remaining products in their original order. Product identification is explicit, never inferred from a name, category or weight. Real product weights and the 31.5 kg parcel limit still apply. Orders without a complete applicable pair retain the existing allocation.

Rules are keyed by a stable string ID and contain product_ids (an array of positive product or variation IDs), units_per_parcel (2), exclusive (true), remainder (‘legacy’) and optionally sync_shipments (boolean, default false). The filter receives the rules array and the WC_Order. Selecting a parent product includes its variations; select individual variation IDs to restrict sizes. Overlapping rules, fractional paired units, incompatible services and overweight pairs stop export before requesting labels. A rule’s allocation is frozen in the export manifest; changing or removing a rule does not repack an export already started.

With sync_shipments true, orders with complete pairs synchronize their confirmed parcels even if the general synchronization setting is off. Shiptastic must be active. This does not enable shipment status changes. Existing generated, unprinted Germanized Pro packing slips are updated after successful allocation commits. Document rendering and surplus-document deletion are deferred during allocation changes and are retried using the existing label-free synchronization action if necessary. Packing slips must be printed after the PLC export and successful synchronization. Shipments already shipped, tracked, labelled or locked, and packing slips already sent to the warehouse, block a new grouped export for manual resolution. Other orders retain their existing document workflow.

The complete parcel allocation, goods values and sender/recipient addresses are saved before the first PLC shipment request. Export retries retain this allocation, including pending services, after refunds or product/order edits. While synchronization is enabled, PLC-owned shipments with confirmed tracking retain their contents during Shiptastic’s automatic validation, even if their status remains processing. Corrections to an export already started require checking PLC and manual resolution. Older partial exports without a saved allocation stop for manual resolution; they are not rebuilt from current products.

Synchronization creates its own manual “Österreichische Post (PLC)” provider and reuses only this PLC-owned provider on later synchronizations. Existing carriers and the shop’s default carrier are unchanged. Unshipped shipments without tracking or labels may be split, reassigned or replaced to match PLC parcels. Shipped, tracked and locked shipments are preserved; conflicting quantities are reported in the order’s PLC information box and notes.

Use the order action “Synchronize PLC parcels to Shiptastic (no new labels)” to retry synchronization independently of exporting labels. Parcel allocations are recorded for new exports from this version, even while synchronization is disabled. Older exports without allocation records are not reconstructed from current products. Ambiguous parcel matches or missing/ambiguous Post tracking numbers require inspection in PLC and are not assigned by guessing. Shiptastic supports whole item quantities; fractional PLC quantities cannot be synchronized.

The separate “Mark synchronized shipments as shipped” setting may trigger Shiptastic customer emails and order automation. With it unchecked, existing shipment statuses are retained; newly split shipments inherit the source status, or start as processing if no source exists. Existing shop automations continue to apply independently.

Important notice: Before the plugin can do its job a WSDL-endpoint, clientID, orgUnitId and orgUnitGUID is required, which can be retreived by the Austrian Post.

FAQ

In which countries does the plugin work?

This plugin is best suited for customers of the Austrian Post, who use the PLC manger.

Which prerequisites are necessary for using our plugin?

WooCommerce 8.2 or newer has to be installed and also an account at the Austrian Post has to be there. You will get all required data like WSDL-endpoint, clientID, orgUnitId or orgUnitGUID from the Austrian Post directly. You will find more information on www.post.at

WSDL endpoints must use HTTPS on post.at or its subdomains, including Austrian Post demo endpoints. Custom endpoints are not supported. PHP SOAP and DOM extensions are required.

Screenshots

Changelog

1.4.0

  • Adds opt-in, filter-configured product pairs in exclusive parcels, with odd units packed using the existing rules.
  • Retains real shipment weights, original order-line quantities and immutable export allocations.
  • Allows rule-specific Shiptastic synchronization and updates Germanized packing slips after commit, with label-free recovery.
  • Leaves default packing and other installations unchanged without explicitly configured rules.

1.3.1

  • Deducts item quantities refunded before export and uses discounted order values including VAT.
  • Fixes customs fallbacks, overweight item handling, zero/missing weights and floating-point packing boundaries.
  • Saves the complete export allocation before contacting PLC so partial retries retain original services, contents, values and addresses.
  • Keeps Shiptastic quantities and item data aligned with the frozen PLC allocation, including pre-export refunds.

1.3.0

  • Adds optional synchronization of confirmed PLC parcels, item allocations and tracking numbers into Shiptastic.
  • Mirrors weight-based parcel splitting and uses a dedicated Austrian Post carrier without changing existing providers.
  • Adds a separate, default-off option to mark synchronized shipments as shipped.
  • Adds label-free synchronization retries, conflict reporting and transactional reallocation.
  • Keeps existing export behavior when synchronization is disabled.

1.2.2

  • Selects the Austrian Post tracking code per parcel while preserving genuine multi-package orders.
  • Adds clickable parcel tracking links to both WooCommerce order administration screens.
  • Preserves ambiguous historical code lists and displays a warning for manual inspection.

1.2.1

  • Fixes SOAP method signature compatibility with PHP 8.5 while retaining PHP 7.4 support.
  • Supports HPOS and legacy WooCommerce order storage, including both order administration screens.
  • Secures AJAX, settings, product fields, bulk actions and tracking output.
  • Restricts SOAP services and imported resources to Austrian Post HTTPS endpoints.
  • Prevents duplicate confirmed exports and preserves shipment data on failures.
  • Requires WooCommerce 8.2+, WordPress 6.2+ and PHP 7.4+.

1.1.9

  • fixes potential division by zero

1.1.8

  • splits order into multiple packets if the weight is too high

1.1.7

  • adds weight to the order

1.1.6

  • checked version & minor updates

1.1.5

  • added translations

1.1.4

  • PHP 8.1 compatibility check and added option to automatically move order to completed, when sent to plc successfully.

1.1.3

  • Bug fix if one of the customs options is not set

1.1.2

  • Made it possible to set packet type on product layer

1.1.1

  • Removing whitespaces before and after PLC settings

1.1.0

  • Made it possible to communicate with PLC without entering customs options

1.0.2

  • Changed readme.txt a bit and added austrian translation

1.0.1

  • Added new languages

1.0.0

  • Initial release