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.

Agora Commerce
Overview
Topics
  • B2B shops and dealer portals
  • Employee shops
  • Catalogues and pricing
  • Procurement and approvals
  • Ordering models
FeaturesDemos
Technology & operations
  • Integrations
  • Shop operations and administration
  • Technology and access
Recurring orders
  1. Software
  2. Agora Commerce
  3. Features
  4. Recurring orders

Agora Commerce · PROWERB’s own B2B shop software

Give recurring requirements a clear schedule.

Consumables, equipment and recurring requirements at a location do not have to be assembled from scratch each time. An ordering schedule records the required items and intended interval.

Explore recurring requirementsDiscuss your shop project
RheinwerkOur company catalogue

Recurring requirement

PowerCore Pro

Contract module · Pro version

Quantity per execution
2
Intended schedule
Monthly
Plan status
Active in the example

Before every execution

  1. Check current availability and terms
  2. Apply current purchasing rules
  3. Associate execution with its order
View an execution’s order
Example view of an individually designed Agora shop. The steps explain the workflow using fixed example data.

Agora makes the next planned step understandable. Current prices, quantities and purchasing rules still matter when an order repeats. A schedule is therefore distinct from an order that has actually been executed.

How it works.

  1. Select the items

    Recurring requirements are defined with products and quantities within the intended company context.

  2. Set the interval

    The schedule records when the next ordering step is intended. Responsibility and the desired workflow are configured for the shop.

  3. Review execution

    Current terms and relevant limits are considered before further processing. The planning status remains distinguishable from the order status.

  4. Handle exceptions

    If an intended price limit or another rule is not met, the responsible person must understand why the request needs attention.

Planning stays connected to current purchasing conditions.

Saved requirements do not override current catalogue and purchasing rules. The next scheduled date is not a delivery confirmation either. We define which steps are prepared and where your team continues to make decisions. Payment and logistics are considered within the project scope.

What we configure for your shop.

Items and quantities
Which requirements recur, and which items may change between executions?
Schedule
Interval, next execution and intended processing are defined together.
Price limits
Which changes may the schedule accept, and when is another decision required?
Responsibility
Who reviews exceptions, adjusts requirements and assesses the next ordering step?

Frequently asked questions.

Are payments executed automatically?

A recurring order schedule does not imply automatic payment. Payment method and execution are agreed for the shop model.

What happens when prices change?

Current terms and configured price limits must be considered before the next execution. Handling of discrepancies is defined during setup.

Fits your workflow.

Ordering modelsQuick orderBudgets and cost centresCatalogues and contract prices

How should your shop use this feature?

We develop Agora and use it to build your individual B2B shop. Let us discuss the workflow, configuration and integrations you need.

Discuss your shop project