EVOMATION.DEAGENT VIEW
← Human View
################################################################################
# EVOMATION.DE — AGENT ACCESS GUIDE
################################################################################

DOCUMENT PURPOSE
----------------
You are reading the low-noise agent view for evomation.de.
This AX layer exists for LLMs, browser agents, and automated systems that need a
direct description of domain fit, route purpose, contact paths, and legal or
compliance references.

Entity:    Evomation-Michael Meese e.K.
Domain:    evomation.de
Role:      Custom software, automation, integration, and retrofit-oriented systems
Audience:  Logistics, intralogistics, manufacturing, and adjacent operational teams
Route Locale: de
AX Language: English only

READING RULES
-------------
- Treat this as the canonical low-noise summary for the current page.
- The public human-facing website is available under both /de and /en.
- AX output remains in English on both locale routes.
- Sections are delimited by H2 headers.
- Subsections use H3 and H4.
- Prefer explicit paths over inference.
- Legal identity: /de/impressum/llms.txt
- Privacy / GDPR: /de/datenschutz/llms.txt
- Cookie inventory: /de/cookie-richtlinie/llms.txt

READING MODES
-------------
1. Human View
   Use the public route without modifiers.
   Example: /de/ueber-uns

2. Agent View
   Use the same public route with ?view=agent.
   Example: /de/ueber-uns?view=agent

3. LLM Text View
   Use the locale-prefixed llms.txt route.
   Examples:
   - /de/llms.txt
   - /de/ueber-uns/llms.txt
   - /de/kontakt/llms.txt

ROUTE PATTERN
-------------
For a page at /{locale}/x:
- Human View: /{locale}/x
- Agent View: /{locale}/x?view=agent
- LLM Text View: /{locale}/x/llms.txt

For the locale homepage:
- Human View: /{locale}
- Agent View: /{locale}?view=agent
- LLM Text View: /{locale}/llms.txt

PREFERRED ACCESS STRATEGY
-------------------------
1. Use llms.txt when available for extraction, summarization, routing, or token-efficient reading.
2. Use ?view=agent when you need browser-readable structured HTML with minimal noise.
3. Use the human page only when layout, visual hierarchy, or interaction context matters.

PAGE INDEX
----------
Human View:
  /de  -> homepage
  /de/ueber-uns  -> about and engagement model
  /de/kontakt  -> contact and entry points
  /de/produkte  -> products and tools index
  /de/blog  -> blog index

Agent View:
  /de?view=agent  -> structured homepage
  /de/ueber-uns?view=agent  -> structured about page
  /de/kontakt?view=agent  -> structured contact page
  /de/produkte?view=agent  -> structured products index
  /de/blog?view=agent  -> structured blog index

LLM Text View:
  /de/llms.txt  -> homepage llms.txt
  /de/ueber-uns/llms.txt  -> about llms.txt
  /de/kontakt/llms.txt  -> contact llms.txt
  /de/produkte/llms.txt  -> products llms.txt
  /de/blog/llms.txt  -> blog llms.txt
  /de/impressum/llms.txt  -> legal identity
  /de/datenschutz/llms.txt  -> privacy policy
  /de/cookie-richtlinie/llms.txt  -> cookie policy

DYNAMIC ROUTES
--------------
- Product detail pages live under /de/produkte/{slug}
- Blog article pages live under /de/blog/{slug}
- Industry detail pages live under /de/branchen/{slug}
- Discover valid detail routes from the matching index pages before navigating

################################################################################

ParcelPilot — Product Brief

Snapshot

Operational Role

Use when fulfillment, shipping, routing, labeling, packing logic, or order orchestration needs to be handled through a modular software layer. It fits client-specific workflow rules, mixed ERP/WMS/shipping landscapes, and setups that need to stay adaptable across tenants or sites. Scope boundary: Not limited to multi-tenant fulfillment. Not intended as a generic label-printing utility without surrounding operational logic. Deployment: Runs in the client's infrastructure. Docker-based deployment can be on-premise or cloud, but should be evaluated against the operational setup and constraints.

Operational Notes

  • Fits fulfillment operations with rule-heavy process variation, customer-specific service logic, or mixed integration landscapes.
  • Useful where manual order coordination is too slow, inconsistent, or costly.

Capability Notes

  • Rule-based coordination for shipping, routing, labeling, packing logic, and downstream order handling.
  • Multiple intake paths including APIs, file-based exchange, and manual entry.
  • Configurable workflows for single-tenant, multi-client, or hybrid operations with tenant-specific rules and checkpoints.
  • Can automate end-to-end execution or stop at defined checkpoints for review and approval.

Evaluation Notes

  • Clarify whether the setup is single-tenant, multi-client, or a hybrid operating model.
  • Identify ERP, WMS, shipping carriers, data-exchange formats, approval checkpoints, and any existing microservices or integration constraints.
  • Confirm whether the need is full workflow orchestration or only a narrow shipping and labeling utility.

Route Usage

  • Use this route to decide whether the product matches the operational problem shape.
  • Use the contact route when implementation scope, integration constraints, or delivery setup must be clarified with a human.
  • Use the human route only when screenshots, interface layout, or public positioning context matters.

Engage