Skip to content
PROWERB
Services
Industries
Cases
Lab & Software
Company
DENeeds Check →
Services
Industries
Cases
Lab & Software
Company
LanguageDEEN
Start Needs Check →
PROWERB — Elevating Brands

Marketing Operations Backbone since 1979. Promotional products, logistics, kitting and digital commerce. One partner with its own operations in Kleve.

Elevating Brands — since 1979.Kleve · Düsseldorf · Dortmund · Lüdinghausen
Services
Logistics & fulfillmentPromotional products & merchandiseDigital commerce & marketplaceEvents & campaignsKitting, textile & ESGTech & AI
Company
About usLocationsHow we workSustainabilityCareersContactInternationalPress & news
Resources
GuidesInsights archiveGlossaryDownloadsTools & calculatorsCosts & calculationCompare operating models
Contact
PROWERB, Huissener Str. 7–947533 Kleve+49 (0)2821 7218-0info@prowerb.de
© 1979–2026 Prowerb GmbHLegal notice (German)Privacy policy (German)Terms (German)BrandDEEN

All rights reserved. Subject to change. Text and images on this website have in part been created or edited using artificial intelligence.

Prowerb Software Lab

Prowerb OS

Plan campaigns. Control fulfilment.

ProAktion connects campaign planning, recipient lists, approvals, fulfilment and shipping. Customers co-control in Atlas while operations runs the case in Nexus.

Start Prowerb OS demo
Prepare the handoff

Prepare the handoffOperations reviews PR-1042: stock checked, approval pending. 12 ordered, 10 prepared, 2 pending. Resolve the pending approval before handoff.

Enlarge view (opens a new tab) ↗
Product overview ↑
  • 01Experience liveExperience how Atlas and Nexus connect customer view, order status, and operations in one digital workflow.
  • 02Atlas & NexusPlan campaigns, prepare products and recipients, and track stock and shipping in Atlas. PROWERB organises delivery in Nexus.
  • 03Technology & securityLearn how roles, data, interfaces, and operational workflows work together in Prowerb OS.
  • 04Atlas customer portalBring orders, status, documents, and communication into a digital customer portal connected directly to operational processes.
  • 05ProAktion & fulfilmentRun campaign logistics, orders, exceptions, and status communication in one shared fulfilment workflow.
Connected workflow

One case through shipping.

Example PR-1042: 12 team jackets ordered, 10 prepared, 2 pending. Resolve the shortage and customer decision first. “Ready” means that data and approvals are complete for the agreed handoff. The warehouse must confirm receipt; “shipped” follows only after dispatch feedback. These states remain separately traceable.

  1. 01

    Capture

    The campaign, order, positions, dates and ownership form the operational frame.

  2. 02

    Prepare

    Imports, stock, shipping requirements and open decisions come together.

  3. 03

    Hand over

    The approved handoff package reaches fulfilment and shipping with complete context.

  4. 04

    Report back

    Progress, exceptions and completion update Nexus and the customer view in Atlas.

New data becomes a manageable case.
Intake and import

New data becomes a manageable case.

ProAktion assigns order and address data to the right process and exposes deviations before the handoff.

  1. 01

    Assign

    Source, campaign, order and positions are connected through clear references.

  2. 02

    Reconcile

    Quantities, addresses and required details are checked against the expected case.

  3. 03

    Prepare

    Valid data flows into scheduling while deviations create a clear clarification case.

Stock, dates, approvals.
Scheduling and approval

Stock, dates, approvals.

Nexus connects available positions, shipping windows and ownership. Atlas gives customers the context to approve and co-control the campaign.

  1. 01

    Reserve stock

    Positions and quantities are planned for the intended case.

  2. 02

    Secure the date

    Production, inbound and shipping windows determine the order of work.

  3. 03

    Obtain approval

    The decision includes context, impact and the resulting operational step.

Fulfilment

From handoff to shipping.

Approved addresses, positions, quantities, dates and shipping requirements form the handoff. Processing, warehouse status and shipping flow back into Nexus and Atlas.

  1. 01

    Ready

    All required data and decisions are present on the case.

  2. 02

    In progress

    The owner, timing and progress of the fulfilment task stay visible.

  3. 03

    Shipped

    Shipping information and completion flow back into operations and the customer portal.

Resolve deviations directly.
Exceptions

Resolve deviations directly.

Missing data, stock conflicts and handoff errors are handled with their cause, impact, owner and due date on the case.

  1. 01

    Clarify data

    Incomplete or conflicting information leads to a targeted question.

  2. 02

    Adjust the plan

    Stock or timing deviations update the task, priority and next decision.

  3. 03

    Continue the handoff

    After resolution, the workflow resumes at the intended transition.

Every step has an owner.
Roles and ownership

Every step has an owner.

Projects, operations, fulfilment and customers use the same process logic in their respective views.

  1. 01

    Project management

    Controls the campaign frame, dates, customer decisions and escalations.

  2. 02

    Operations

    Handles imports, scheduling, approvals, exceptions and handoffs in Nexus.

  3. 03

    Fulfilment

    Takes approved tasks and reports processing and shipping back.

  4. 04

    Customers

    See milestones and make intended decisions in Atlas.

Explore integrations and operating ownership ↗
System handoffs

APIs connect orders, warehouse and shipping.

Read models, APIs and events connect order, warehouse and shipping systems of record through defined handoffs and stable case references.

  1. 01

    Order data

    Campaigns, positions, addresses and dates are accepted through stable references.

  2. 02

    Warehouse data

    Stock, reservations and inbound support planning and approval.

  3. 03

    Shipping data

    Handoff, shipping progress and completion are assigned to the original case.

Progress becomes controllable.
Reporting and Power BI

Progress becomes controllable.

Power BI live reports connect campaign progress with stock, budgets and track and trace. Automated Excel exports and interfaces bring the data into existing analysis workflows.

  1. 01

    Campaign status

    Planning, approvals, fulfilment and shipping remain traceable along the case.

  2. 02

    Stock and budgets

    Live data shows inventory trends and budget control in the relevant campaign context.

  3. 03

    Process further

    Excel exports and APIs provide approved data for further analysis.

Campaigns ready for fulfilment.
Use cases

Campaigns ready for fulfilment.

The workflows suit campaigns with many records, fixed dates and several operational handoffs.

  1. 01

    Shipping campaigns

    Address import, packing, shipping and progress communication for time-bound campaigns.

  2. 02

    Launch and onboarding boxes

    Positions, recipient groups, dates and fulfilment for planned rollouts.

  3. 03

    Recurring campaigns

    A standardised flow for new data waves, approvals and shipping handoffs.

Frequently asked questions

ProAktion explained.

Answers about the workflow, fulfilment and customer view.

What does ProAktion control?

ProAktion connects the campaign case, import, planning, approval, exceptions and fulfilment handoff.

How does fulfilment stay connected?

Approved tasks reach fulfilment with complete context; progress and shipping flow back to the case.

What do customers see?

Atlas shows the approved milestones, decisions and progress information from the same case.

Prowerb OS demo

Follow campaigns through fulfilment.

Open the demo directly and experience ProAktion working with Nexus and Atlas.

Start Prowerb OS demo