Proposed rentable inventory
Define the proposed pallet-position, rack, zone or capacity model plus availability, allocation, time and service rules.
Specialist model evaluation
Map pallet-position or capacity rentals to StoRegister's customer, agreement, billing and reporting baseline while keeping pallet scans, goods inventory, movements and logistics requirements explicit.
This is an evaluation guide, not a universal compatibility claim. Pallet storage fit must be demonstrated and written into scope before purchase.
Direct answer
StoRegister can be evaluated for operators that rent pallet spaces by mapping customers, rentable capacity, agreements, pricing, recurring billing, payments, documents and reporting. Pallet-level scanning, goods inventory, locations and movements, FIFO or FEFO, fulfilment and carrier workflows are not assumed and require separate confirmation.
Operating model
Start with the verified platform baseline, then translate model-specific inventory and exceptions into testable requirements.
Define the proposed pallet-position, rack, zone or capacity model plus availability, allocation, time and service rules.
Test enquiries, quotations, reservations, customers, agreements, documents, changes and termination.
Test rates, deposits, recurring charges, invoices, payments, overdue work and the required reporting.
Connected lifecycle
Use representative records and exceptions from availability through account closure and reporting.
Map the proposed pallet-position, rack, zone or capacity model and availability.
Exercise enquiry, quotation, allocation, customer, agreement and document steps.
Test required time, capacity and service-based charges, invoices, payments and overdue work.
Test capacity changes, release, account history and facility or portfolio reporting.
Six requirement groups
Each group should produce a visible demo scenario, a supported answer and an owner for unresolved dependencies.
Define the proposed pallet-position, rack, zone or capacity model plus availability, allocation, time and service rules.
Test how pallet storage pricing, deposits, recurring charges, taxes, promotions and add-ons should be represented.
Map enquiry, quotation, reservation, customer setup, agreements, payments, amendments and move-out.
Confirm which tasks belong in Sleek Web, which supported context is needed on mobile and who owns each exception.
List every specialist provider, hardware, regulatory, data-exchange and API requirement; assess compatibility separately.
Define facility and portfolio views, representative test cases, exclusions, owners and written acceptance evidence.
Right task, right surface
A feature available somewhere in the platform is not automatically available in every plan, application, channel or storage-model configuration.
Run the agreed lead, availability, customer, rental, billing and reporting workflows from the operator application.
Back-office operationsGive authorised teams a focused route to supported operational context on iOS and Android, subject to plan and device scope.
On-site contextProvide configured booking and tenant-account journeys where the selected plan, model and implementation support them.
Customer journeyAssess documented integrations and approved API use cases against the required provider, market, version and commercial scope.
Controlled connectivityEvidence before commitment
Make both sides visible so a familiar label never becomes an unsupported capability or compatibility promise.
The locked platform pages support these concepts.
These details depend on the operation and agreed implementation.
Evidence-first evaluation
Bring the model and exceptions; leave with demonstrated coverage, exclusions, ownership and commercial scope.
Provide representative inventory, customers, terms, providers and exceptions.
Demonstrate the required enquiry, rental, finance and closure scenarios.
Exercise specialist, negative, recovery and integration cases.
Document supported scope, exclusions, owners, price and proposal terms.
Platform evidence
Review platform coverage, feature boundaries and the evidence scorecard before comparing proposals.
Related storage models
Use the Product Hub for the complete directory and keep supported categories distinct from specialist evaluations.
Storage model questions
Use these answers to distinguish verified platform evidence from operation-specific confirmation.
Pallet storage management software may connect rented pallet positions or capacity with customers, contracts and billing. Specialist systems may also track individual pallets, goods, warehouse locations, scans, movements, FIFO or FEFO, fulfilment and transport.
StoRegister can be evaluated by mapping pallet-space or capacity rentals to its verified customer, rentable-space, agreement, billing, payment, document and reporting baseline. Pallet storage is not currently listed as one of the four supported storage models, so fit must be demonstrated and documented.
Bring representative pallet-position, rack, zone or capacity records, prices, availability rules and exceptions. StoRegister can assess how they map to its space and rental concepts; the final supported configuration must be recorded.
This page does not claim pallet-level barcode, RFID, rack, bin, scan or movement tracking. Define identifiers, volumes, scan events, evidence and reporting so configuration, integration or a specialist system can be assessed.
This page does not claim goods-inventory management for SKUs, lots, batches, serial numbers or expiry dates. Document the required hierarchy, ownership, quantities, locations, movements and controls to define the system boundary.
This page does not claim FIFO, FEFO, put-away, picking, packing, fulfilment or dispatch capability. Demonstrate each required event, decision, exception, integration and charge before commitment.
Rates, deposits, fees, taxes, add-ons, invoices, recurring payments and reporting form part of the platform baseline. The proposed pallet-capacity, time and service pricing model must be demonstrated and documented.
Bring sample capacity and customer records, contracts, rate and service models, pallets and goods data, locations and scans, movements, FIFO or FEFO, picking and dispatch, providers, reporting, exceptions and acceptance criteria.
Yes, subject to an agreed proposal. StoRegister can scope first-system setup using agreed business information, or migration from another platform using an agreed supported data set. Migration depends on source access, data quality, provider compatibility, mapping and acceptance. Both routes can include selected application and compatible-integration configuration, go-live preparation and paced adoption guidance. Assistance requests can be raised 24/7; fees, channels, staffed coverage, response and resolution targets, responsibilities, acceptance and the service endpoint are defined in the proposal and applicable agreement.
Build a relevant walkthrough
Bring representative inventory, customers, rental terms, billing rules, providers, specialist exceptions and acceptance criteria.