Apaczka Integration

The Apaczka integration extends the system with the ability to create and manage transport / courier orders across many carriers from a single unified wizard. It lets you compare offers (price, delivery time, service type) and automates shipment creation and status tracking – without logging into an external portal.

Why Apaczka?

Key benefits:

  • Access to a wide range of carriers in one place.
  • Dynamic filtering of available products based on selected add‑ons (you first pick add‑ons – then only compatible services are shown).
  • Ability to define multiple packages (rows) within a single order.
  • Standardised wizard – consistent with other TMS integrations.
  • Automatic tracking and status updates inside Business Central.
  • Support for common additional services (insurance, COD, drop-off / pick-up points, special delivery options).

Prerequisites

You need an active Apaczka account plus integration credentials (Application Identifier / Secret). API permissions must be enabled in the Apaczka panel.

Configuration

  1. Open page: TMS | Setup.
  2. In section 🔗 External Integrations choose: Apaczka.
  3. Set Test Mode (recommended: Enabled in sandbox environments).
  4. Choose Default Logistic Service – e.g. TMS (initial default used in the wizard if none selected yet).
  5. Choose Preferred Payment Type – typically: Collective Invoice.
  6. Enter Application Identifier e.g. 234234_xTOxlv7DTFeWefliG7SmEov.
  7. Enter Application Secret (value available in the Apaczka panel – store securely).
  8. Click Validate Settings to test the authentication.
Tip

Test Mode allows creating orders without costs – use it in Sandbox. Disable it in Production after finishing tests.

Ordering Process

A new order can be created from a sales document, warehouse shipment, or from the list of existing transport orders.

Apaczka wizard steps:

  1. Address data (shipper, recipient, contact details, addresses).
  2. Packages (you can add any number of lines – each line is a separate parcel / element of the shipment).
  3. Add‑ons (you pick additional services – the later product list will only show compatible offers).
  4. Product (search and select the carrier service matching package parameters and add‑ons).
  5. Additional information (references, instructions, optional carrier / product specific fields).
  6. Summary (confirmation and order placement).
Important

Unlike the GlobKurier integration – in Apaczka the order is: Add‑ons -> Product. An add‑on can restrict the set of available services, so you choose it earlier.

Status & Tracking

Shipment statuses are synchronised automatically on a schedule (or manually on demand). A timeline of events (time, location, description) is available. Differences in Apaczka status naming are mapped to the TMS standard.

Add‑ons (Additional Services)

Example categories of available add‑ons:

  • Insurance
  • COD (Cash on Delivery)
  • Drop-off / Pick-up point
  • Notifications (SMS / e-mail)
  • Return of documents / packaging
  • Delivery time windows

Apaczka specific behaviour:

  1. Add‑on selection happens BEFORE retrieving the product list.
  2. The product list filters dynamically – shows only services compatible with the currently selected set of add‑ons.
  3. Changing the set of add‑ons requires re-searching services (system does this automatically after confirming the change).
  4. Collisions (mutually exclusive add‑ons) are validated in real time.
Tip

If the number of returned offers is small – try reducing selected add‑ons and search again.

Multiple Package Lines

Apaczka lets you add multiple package lines. Each row contains dimensions, weight and quantity. The system sums parameters where required (e.g. verifying total weight limits) and at the same time retains per‑package detail for labels.

Note

Removing or changing a single line may require refreshing the product list (if the change affects compliance with add‑on or carrier constraints).

Common Issues

Problem Solution
Authorisation error Check Identifier / Secret and whether test mode matches the credentials. Verify API activation in Apaczka portal.
No products after picking add‑ons Remove some add‑ons and search again – they may have narrowed the list to zero. Check package parameters.
No label after submission Ensure the order was correctly registered and accepted. Try downloading the label again from the order card.
Statuses not updating Run the manual update action or check integration error log (e.g. request limit).
Parameters rejected Verify dimensions / weight of single parcels – some products have per‑item and aggregate limits.

Best Practices

  • Start in test mode and compare results with the Apaczka panel before switching to production.
  • Keep the add‑on set minimal – each additional condition narrows the product list.