Define devices & rules
Define device types, contacts, price limits, parts quality and required documentation.
Business · Device fleets · Device lifecycle
Manage device fleets with a clear process.
From consulting and procurement through rollout and repair to take-back, buyback and retirement: ReparARTur combines recurring device processes across the full device lifecycle in one central service.
One point of contactfor repairs, questions and approvals
Batch repairsregister and process multiple devices in a structured way
Clear approval rulesso standard cases keep moving
Status & documentationtraceable for each repair case
Typical B2B cases
Repair service for recurring device cases.
A structured fleet service is most useful when devices require recurring repairs, maintenance, returns or replacement rather than a one-off repair. To start, clear device types, approval rules and a clean batch process are enough; a more extensive RaaS model can later be built on real operating data.
Employee smartphones & tabletsDisplay, battery, rear cover, charging issues and device protection with asset mapping and defined approval limits
Laptop & notebook fleetsCleaning, battery, SSD/RAM, fans and modular repairs as a recurring lifecycle process
Gaming, streaming & eventsControllers, consoles, headsets and other higher-value equipment with heavy use and recurring wear
IT service providers & retailersReparARTur as a repair backend for returns, defective devices or predictable standard cases
Fleet service first · RaaS later
Build a reliable process first.
ReparARTur can act as the central point of contact for ongoing repair handling. At the start, the focus is not on a rigid subscription: standard cases, batch jobs, approval limits and documentation are first proven in practice. Once volume and processes are reliable, this can develop into a broader Repair-as-a-Service model.
01
Central intake
One shared process for smartphones, tablets, laptops, controllers, consoles, handhelds and higher-value gaming and streaming equipment.
02
Asset assignment
Device, model, serial number or internal asset ID can be assigned to each repair case.
03
Agreed price limits
For example: automatically approve repairs up to €100 and request approval above that.
04
Batch handling
Send, process, return or invoice multiple devices together.
05
Device protection & rollout preparation
Smartphones and tablets can be equipped in batches with cases, tempered glass or privacy screens before return or rollout.
06
Device Lifecycle interface
Asset IDs, repair status, return, replacement and retirement can be connected structurally to existing IT processes.
07
B2B consulting & procurement
Select devices and accessories to match use case, budget, standardization and future service requirements, with procurement available on request.
08
Buyback & take-back of retired device fleets
Evaluate retired smartphones, tablets, laptops and other suitable devices in bulk and, after assessment, purchase them or route them into an agreed recovery process.
Optional after pilot
Stock spare parts only once demand is predictable.
A customer-specific minimum stock can be agreed for predefined device fleets. This means common faults do not have to wait for parts sourcing after the device arrives.
ExampleFleet of 400 identical smartphones
individually agreedDisplays10 reservedMinimum stock 5
Batteries8 reservedMinimum stock 4
Camera modules4 reservedas needed
Back covers5 reservedas needed
Customer Reserved Stock
The customer funds an agreed parts inventory. ReparARTur stores and manages it exclusively for that device fleet.
ReparARTur Stock
Selected frequently needed parts are stocked by ReparARTur. Availability and storage costs are reflected in the agreement.
Reserved parts make sense only for suitable and predictable device fleets. Scope, ownership, minimum stock and replenishment are agreed in advance.
Device Lifecycle interface
Repair as part of the device lifecycle.
For businesses, a repair is rarely an isolated event. The device belongs to an asset, a user, a cost area and a lifecycle status. ReparARTur can connect this information structurally with the repair process.
01
Asset assignment
Asset ID, serial number, device type, location or cost center can be assigned to the repair case.
02
Return status
For example: registered, shipped in, received, diagnosis, approval, repair, return shipping, completed.
03
Lifecycle events
Repaired, replacement recommended, not economical, return to stock or retirement can be documented.
04
Import & export
Structured CSV/table formats can initially be used for device inventories, batch orders and status feedback.
05
API / webhook possible later
At sufficient volume, a direct connection to existing asset, MDM/UEM, ITSM or service processes can be implemented.
Wichtig: A direct API, webhook or manufacturer integration is currently not a finished standard product. Data fields, interface format, authentication and target system are defined per business customer.
B2B consulting & procurement
Not just repair – choose the right equipment from the start.
ReparARTur can support businesses in selecting and procuring devices and accessories. The focus is not on individual brands but on use case, budget, serviceability, standardization and total lifecycle cost.
01
Assess requirements
Capture user groups, work environment, performance, mobility, ports, accessories, security and budget requirements.
02
Compare models
Compare suitable device classes and specific models using transparent criteria.
03
Standardize
Use a sensible limited set of device types, chargers, docks, cases and spare parts to simplify operations and support.
04
Support procurement
On request, obtain offers and availability, bundle accessories and prepare procurement for agreed quantities.
05
Prepare rollout
Device protection, accessory assignment, asset mapping and handover can be connected with RaaS and lifecycle processes.
Typical devices
Smartphones, tablets, laptops, monitors, docks, headsets, conferencing equipment and higher-value gaming and streaming equipment.
Typical selection criteria
Price, availability, repairability, spare-parts availability, warranty, accessory compatibility, performance, lifespan and standardization potential.
Procurement by agreement: Manufacturer, distributor or framework-contract terms are only offered when actually available. Prices, lead times and availability are confirmed for the specific requirement.
Fleet buyback & take-back
Do not leave retired devices sitting unused.
Retired device fleets can be assessed in bulk. Depending on device type, age, condition, quantity and market value, buyback, take-back or an agreed recovery route may be possible. A purchase price is only confirmed after sufficient inventory and condition assessment.
01
Record inventory
Record device type, manufacturer, model, quantity, age, storage capacity and available accessories as systematically as possible.
02
Assess condition
Functional, repairable, damaged or no longer economically usable – devices are classified using understandable criteria.
03
Determine buyback value
The valuation considers model, age, condition, quantity, market value, locks and expected refurbishment effort, among other factors.
04
Clarify data & device locks
Before take-back, ownership, existing MDM/UEM bindings, activation locks and the desired handling of existing data are clarified.
05
Document the handover
Device lists, serial numbers or asset IDs can be documented in a structured way for handover and internal traceability.
06
Reuse before disposal
Suitable devices may be refurbished, used for parts or routed to an agreed recycling path depending on condition.
Typical fleets
Business smartphones, tablets, laptops, notebooks, monitors, docks and other standardized IT equipment after prior assessment.
Helpful for an initial valuation
A device list with manufacturer, model, quantity, approximate condition, age, storage capacity and information on MDM/UEM or activation-lock status.
Wichtig: No blanket buyback and no fixed purchase price before assessment. Only devices from verifiable ownership or inventory are accepted. Data wiping or evidence of deletion/destruction is only offered when the process, responsibilities and required evidence have been explicitly agreed in advance.
Fleet service process
One process for recurring repairs.
Plan spare-parts stock
Reserved parts and minimum stock levels can be agreed for common models.
Register devices in batches
Individual devices or batch orders are recorded with asset ID, fault description and requested service.
Assess & approve
Standard cases within the agreed limit proceed directly. Deviations are sent back for approval.
Repair & update status
Every case remains traceable via a repair ID. This can later evolve into a business portal.
Return shipping & billing
Individual or batch return shipping and consolidated billing on the agreed cycle.
Approval logic
Fewer questions for standard cases.
Controllerup to €70repair automatically
Smartphonesup to €120repair automatically
above price limitApprovalrequest before repair
not economical to repairFeedbackdecide repair or replacement
The values are examples only. Price limits and approval rules are defined per customer.
Bulk device protection: For larger fleets, cases and screen protectors can be installed in batches. Pricing is based on quantity, device type, selected accessories and supply model.
Who is it for?
When repairs occur regularly.
Companies with device fleetsSmartphones, tablets, laptops and other mobile work devices – from selection and procurement through repair and lifecycle
IT service providersReparARTur as the repair partner behind the scenes
Retailers & refurbishersReturns, defective devices and recurring standard cases
Gaming, streaming & eventsControllers, consoles, Stream Decks, headsets, microphones and higher-value equipment with heavy use
B2B FAQ
Questions about device fleets, RaaS and lifecycle.
Does RaaS require a large contract from the start?
No. A pilot with a few device types and clear standard cases is more useful. The process is expanded only once workflow, volume and approval rules fit.
Can multiple devices be sent in together?
Yes. Batch registration, combined shipping, asset mapping and bundled return shipping can be agreed for suitable B2B processes.
Can ReparARTur use fixed approval limits?
Yes. For example, standard cases up to an agreed price limit can be processed directly, while exceptions are returned for approval before repair.
Is direct ITSM, MDM or API integration already standard?
No. Structured CSV/table workflows are a pragmatic starting point. Direct integrations can be planned individually when volume justifies them.
Can retired devices be taken back or purchased?
After inventory and condition review, purchase, take-back or an agreed recovery route may be possible. There is no fixed price commitment before assessment.
Start small
Test with a pilot process first.
To start, a device list, typical repair cases and your desired approval rules are enough. Then you can decide whether reserved spare parts, consolidated billing or further processes make sense.