Returns Manager: setup and help

The module uses manual delivery lots first, then Warehouse Revolution shipment dates. Otherwise it tries the first order status marked as delivery, the order's delivery date, then the latest order-carrier record date. With no usable date, the delivery-based window has no deadline.

The window uses the latest recorded delivery date and stays pending while order lines are missing from the delivery records. It checks line coverage, not delivered quantities, so a partially delivered line can start the window early. An order-level delivery record covers the whole order.

By default, no. Require a reason starts at No, and a request can be submitted without choosing a reason. Volunteered reasons and details are saved with the return case. If the setting is enabled, the form requires a valid selection from its reason list.

A full withdrawal includes the lower of paid delivery and Cheapest standard delivery, or paid delivery if that setting is empty. Partial withdrawals exclude outbound delivery; faulty, wrong or missing-goods cases include all paid delivery. A quote does not move money.

Yes. Returns Manager uses its own return-request flow and its own case and item records. Its customer controller and case-creation service do not require PrestaShop's native merchandise-return switch to be enabled. Existing native return requests remain a separate workflow.

No. The virtual-product flag alone is insufficient, and the consent setting defaults to off. The module does not collect checkout consent. Its download lookup uses a column absent from standard PrestaShop, so it cannot apply this exclusion on a standard schema.