The Dragon Guard Handheld client communicates with the Dragon Guard backend API exclusively through plain C# POCOs decorated withDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/CodexaCP/DG_APK/llms.txt
Use this file to discover all available pages before exploring further.
System.Text.Json attributes. These data transfer objects (DTOs) are the authoritative contract between the .NET MAUI Android client and the server: no business logic, no EF navigation properties — only the exact fields the API sends or expects. This reference documents every DTO grouped by functional domain so you can quickly locate any model used in authentication flows, item inquiries, warehouse operations, RFID scanning, or shared utility wrappers.
Authentication Models
Authentication DTOs handle login, session state, company access, and new-user registration flows.AuthLoginRequestDto
Submitted to the login endpoint to initiate a session.The user’s email address used as the login identifier. Maps to the
username concept in the backend identity system.The user’s plain-text password. Transmitted over HTTPS and never stored on-device after the request completes.
Optional hardware or OS-generated device identifier. Used by the backend to associate the session with a registered handheld device for RFID profile resolution.
Optional human-readable device name (e.g.,
"HANDHELD-03"). Displayed in the admin console alongside the active session.Must be
true for all Dragon Guard Handheld client requests. Signals the backend to apply handheld-specific policies and to return the Companies list in the response.AuthSessionResponseDto
Returned by the login endpoint on a successful authentication. Contains the bearer token and the list of companies the user may access.The JWT bearer token to attach as
Authorization: Bearer <token> on all subsequent API requests. The handheld stores this in secure local storage.Unique identifier of the authenticated user record in the backend.
The authenticated user’s email address, echoed back for display and local caching purposes.
The user’s display name shown in the handheld UI header and audit trails.
All tenant companies the user is authorized to access, each entry carrying the company identifier and the user’s role within that company.
AuthCompanyAccessDto
Minimal company-access record embedded insideAuthSessionResponseDto.Companies.
The tenant company’s unique identifier. Passed as a route or query parameter in every company-scoped API call.
Role assigned to this user in this company. Common values:
"OPERATOR", "SUPERVISOR", "ADMIN".AuthRegistrationOptionsDto
Returned by the registration options endpoint to populate the company-selection picker shown during new-user self-registration.The list of companies available for self-registration. Displayed in the handheld picker so a new user can choose which tenant to join.
The role code that will be assigned to newly registered users if the backend does not override it. Defaults to
"OPERATOR".AuthRegistrationCompanyDto
A single company entry withinAuthRegistrationOptionsDto.Companies.
The company’s unique identifier. Used as
CompanyId when submitting the registration request.Short alphanumeric company code displayed alongside the full name.
Human-readable company name rendered in the picker. Also returned by
ToString() for MAUI binding compatibility.RegisterUserRequestDto
Posted to the user-registration endpoint when a new operator signs up from the handheld.The new user’s email address. Must be unique across the tenant.
Plain-text password for the new account. The backend hashes this before storage.
The user’s display name shown in the handheld UI and audit logs.
The target tenant company. When
null, the backend may assign the user to a default company or require an administrator to complete the assignment.Item Models
Item DTOs expose product master data, per-bin stock levels, and full item detail for inquiry screens.ItemInquiryDto
Represents a single item–bin stock record returned by the item inquiry endpoint. Each row describes the item’s attributes alongside the specific bin where stock resides.Tenant company identifier that owns this inventory record.
Internal surrogate key for the item in the backend database.
Business-facing item number (SKU). Displayed prominently in all handheld inquiry screens.
Full item description text.
Unit of measure code for this item (e.g.,
"EA", "CASE", "KG").Classification of the item (e.g.,
"PRODUCT", "SERVICE").Whether the item is active and eligible for warehouse transactions.
true if the item requires lot number assignment during receiving and picking.true if each unit must be assigned a unique serial number.true if the item must have an expiration date recorded on each transaction.Weight per unit. Used for weight-based quantity validation when applicable.
Volume per unit. Used for capacity planning.
Surrogate key of the bin where this stock quantity resides.
Human-readable bin location code (e.g.,
"A-01-01").Descriptive label for the bin location.
Bin classification code (e.g.,
"PICK", "BULK", "STAGE").Whether the bin is currently active and accepting transactions.
true if transactions are blocked for this item–bin combination.Whether the handheld may present this bin as a pick source for this item.
Whether the handheld may suggest this bin as a put-away destination for this item.
Current on-hand quantity for this item at this bin.
ItemSummaryDto
An aggregated stock summary for an item across all bins within a location. Contains the rolled-up total plus the per-bin breakdown.The item number (SKU) being summarized.
Warehouse location code scoping the summary (e.g.,
"MAIN", "ZONE-A").Sum of
StockQty across all bins in the location for this item.Per-bin breakdown rows. Each element is an
ItemInquiryDto describing stock at a specific bin. See ItemInquiryDto for field details.ItemDetailApiDto
Full item master record returned by the item detail endpoint. Includes UOM conversions, tracking flags, quantity positions, and associated images.Unique backend identifier of the item record.
Business-facing item number (SKU).
Full item description text.
Default unit of measure code.
Base (inventory) unit of measure used for all stock quantity calculations.
Unit of measure used on sales orders.
Unit of measure used on purchase orders.
Manufacturer or supplier part number.
Secondary item code used for cross-referencing with external systems.
Conversion multiplier between the purchase/sales UOM and the base UOM.
Whether the item is active and available for warehouse transactions.
Item classification (e.g.,
"PRODUCT", "SERVICE", "COMPONENT").Primary barcode (e.g., EAN-13, UPC-A) used for barcode scanning on the handheld.
Alternate barcode for items with multiple scannable codes.
Requires lot number on all inventory transactions.
Requires a unique serial number per unit on all inventory transactions.
Requires an expiration date on all inventory transactions.
When
true, the system permits QtyAvailable to go below zero for this item.Weight per base unit.
Volume per base unit.
Product category classification code.
Item brand name.
ABC inventory classification (
"A", "B", or "C").Accounting or product group assignment for ledger posting rules.
Branch or division code when the item belongs to a specific organizational unit.
Inventory costing method (e.g.,
"FIFO", "AVERAGE", "STANDARD").Username or email of the user who created this item record.
UTC timestamp when the item record was created.
Username of the user who last modified this item record.
UTC timestamp of the most recent modification.
Total quantity physically present in the warehouse across all bins.
Quantity on open purchase orders (inbound, not yet received).
Quantity committed to open sales orders (outbound, not yet shipped).
Quantity available to promise:
QuantityOnHand − QtyOnSalesOrder + QtyOnPurchOrder (backend formula may vary).Quantity allocated to open production orders.
true when the item’s available quantity has fallen below its reorder threshold.Product images associated with this item. The primary image is marked with
IsPrimary = true.ProductInquiryPageDto
Paginated response returned by the product inquiry list endpoint. Extends standard pagination with an aggregated quantity total.The current page number (1-based).
Number of rows per page.
Total number of product rows matching the query across all pages.
Total page count:
ceil(totalRecords / pageSize).Sum of
Quantity across all rows matching the query (not just the current page). Displayed in the inquiry screen footer.Display label for the quantity column / footer, localized by the backend (e.g.,
"Cantidad", "Quantity").The page’s data rows. See ProductInquiryRowDto for field details.
ProductInquiryRowDto
A single row in the product inquiry result set, representing an item–location–bin stock position.Optional row identifier. May reference the item record or a ledger entry depending on the query mode.
Item number (SKU) for this row.
Item description text.
Secondary item number from the item master’s
Alternative_Code.Scannable barcode for this item.
Primary unit of measure.
Secondary UOM when the item has a purchase/sales UOM that differs from the base UOM.
Item active flag.
Whether the item may carry a negative available balance.
Item status descriptor from the backend (e.g.,
"Active", "Blocked").The item’s default warehouse location code from the item master.
Shelf or zone code within the location.
Warehouse location code for this stock position.
Human-readable location description.
Bin code where the quantity is stored.
Human-readable bin description.
Stock quantity at this item–location–bin position.
Describes what the quantity represents (e.g.,
"OnHand", "Available", "Committed").UTC timestamp when this quantity snapshot was calculated.
Receiving Models
Receiving DTOs represent inbound warehouse receipts — the header document and its individual product lines.ReceivingHeaderDto
The top-level receipt document returned by the receiving list and detail endpoints. Tracks vendor, location, lifecycle dates, and a three-tier status model.Unique identifier of the receiving header record.
Tenant company that owns this receipt.
System-generated receipt document number displayed in the handheld list and header.
Vendor or purchase order number from the external ERP or supplier document.
Supplier/vendor code from the business partner master.
Supplier display name shown on the receipt header card.
Warehouse location code where goods are being received. The computed
DisplayLocationCode falls back to "MAIN" when this is blank.Raw internal status field.
Document-level lifecycle status (e.g.,
"Open", "Released", "Posted").Handheld-side processing status (e.g.,
"Pending", "Partial", "Complete"). When non-empty, takes precedence over DocumentStatus for display via the computed VisibleStatus property.The date the receipt is expected or was recorded.
UTC timestamp when the receiving header was created in the system.
UTC timestamp when the receipt was posted to the ledger.
null if not yet posted.Username of the user who created the receiving header.
Username of the user who posted the receipt.
null if not yet posted.ReceivingLineDto
A single product line within a receiving header. Tracks expected, received, and posted quantities along with bin assignment.Unique identifier of this receiving line.
Foreign key linking this line to its parent
ReceivingHeaderDto.Tenant company identifier.
Backend identifier of the item being received on this line.
Backend identifier of the bin assigned to receive this line.
null if not yet assigned.Human-readable bin location code.
Item number (SKU) for this line.
Quantity ordered / expected on this receipt line (sourced from the purchase order).
Quantity confirmed as received on the handheld in the current session (not yet posted).
Unit of measure for all quantities on this line.
UTC timestamp when this line was created.
Quantity that has already been posted to the inventory ledger from previous sessions.
Quantity still to be received:
QuantityExpected − PostedQuantityReceived. Drives the ShortStatusLabel computed property ("Done" / "Part" / "Pend").Bin code suggested by the backend as the optimal put-away destination. Defaults to
"MAIN".UpdateReceivingLineDto
Payload posted to the update-line endpoint when the operator confirms a received quantity or changes the bin assignment.The quantity the operator has counted and confirmed as received for this line.
The bin where the goods were placed. When
null, the backend retains the previously assigned bin or uses the suggested bin.Shipment Models
Shipment DTOs represent outbound warehouse shipments — the header document and its individual pick/ship lines.ShipmentHeaderDto
The top-level outbound shipment document. Tracks customer, warehouse, planned/actual ship dates, and a three-tier status model.Unique identifier of the shipment header.
Tenant company identifier.
Short company code displayed alongside the shipment in multi-company environments.
System-generated shipment document number displayed in the handheld shipment list.
Customer reference or external sales order number.
Shipment classification (e.g.,
"SALES", "TRANSFER", "RETURN").Domain-specific shipment status (e.g.,
"Pending", "Picking", "Shipped").Document-level lifecycle status (e.g.,
"Open", "Released", "Posted").Handheld-side processing status. When non-empty, takes precedence over
DocumentStatus for display via VisibleStatus.Originating warehouse location code. The computed
LocationCode falls back to "MAIN" when empty.Customer/business partner code from the master data.
Customer display name shown on the shipment card.
Scheduled ship date from the sales order.
Date the shipment was physically dispatched.
null until the shipment is confirmed.Total number of shipment lines on this document.
Sum of ordered quantities across all lines.
true when the shipment has been fully processed and closed against further changes.UTC timestamp when the shipment header was created.
ShipmentLineDto
A single product line within a shipment. ImplementsINotifyPropertyChanged so the MAUI binding layer updates in real time when ShippedQty changes.
Tenant company identifier for this line.
Parent shipment header identifier.
Unique identifier of this shipment line.
Sequential line number within the shipment document.
Current status of this individual line (e.g.,
"Pending", "Picked", "Shipped").Backend identifier of the item to be shipped on this line.
Item number (SKU) displayed on the handheld pick/ship screen.
Item description text.
Unit of measure for all quantities on this line.
Warehouse location identifier for pick source.
Pick source bin identifier.
Pick source bin code displayed to the operator.
Quantity ordered on the sales/transfer order. Acts as the upper bound for
ShippedQty on the handheld.Quantity confirmed as picked in the pick-to-ship workflow.
Quantity entered by the operator as shipped. Automatically clamped to
[0, OrderedQty] by the property setter. Triggers INotifyPropertyChanged for MAUI binding updates.Quantity expressed in the item’s base unit of measure (for UOM-conversion scenarios).
Remaining quantity from the backend’s perspective (may be pre-computed).
Remaining quantity from a second backend source. The computed
RemainingBalance uses RemainingQuantity > 0 ? RemainingQuantity : RemainingQty.Lot number assigned to this line for lot-tracked items.
Serial number for serial-tracked items.
Expiration date for expiration-tracked items.
Weight per unit, used for manifest generation.
Volume per unit, used for manifest generation.
true when this line has been fully processed.UTC timestamp when this line was created.
UTC timestamp of the most recent update.
Quantity posted to the ledger in previous sessions. Used together with
PostedQuantity to compute the ShortStatusLabel.Quantity posted to the ledger (may come from a different API field than
AlreadyPostedQty).UpdateShipmentLineDto
Minimal payload sent to the update-line endpoint when the operator confirms a shipped quantity.The quantity the operator has confirmed as shipped for this line.
Movements & Journals
These DTOs support the warehouse movements log, product journal management, and location selection.MovementsPageDto
A single row in the movements history feed, representing one inventory movement event.Unique identifier of the movement record.
System-generated movement document number.
Backend identifier of the item that moved.
Item number (SKU) of the moved item.
Item description text. The class also exposes a
Description property ([JsonPropertyName("description")]) that reads and writes the same backing field, allowing the backend to send either JSON key.Source bin identifier.
Source bin code.
Source warehouse location code.
Destination warehouse location code for inter-location transfers.
null for intra-location moves.Quantity moved. Positive for receipts/inbound; negative for issues/outbound (convention depends on
movementType).Classifier for the movement (e.g.,
"RECEIPT", "SHIPMENT", "TRANSFER", "ADJUSTMENT").Internal reference document number (e.g., a receipt or shipment number).
External reference document number (e.g., vendor PO or customer SO).
Identifier of the user who recorded this movement.
UTC timestamp when the movement was recorded.
ProductJournalHeaderDto
Header record for a product journal batch. Journals group multiple inventory adjustments into a single document.Unique identifier of the journal header.
System-generated journal document number.
Free-text description of the journal batch.
Default movement type applied to all lines (e.g.,
"ADJUSTMENT", "TRANSFER").Accounting date for the journal posting.
null if not yet set.External reference document number.
Transit location used for in-transit inventory during inter-location transfers.
Journal lifecycle status (e.g.,
"Open", "Posted").Number of lines in this journal batch.
ProductJournalDetailDto
ExtendsProductJournalHeaderDto with the full collection of journal lines.
The individual inventory movement lines within this journal. Inherits all header fields from
ProductJournalHeaderDto.ProductJournalLineDto
A single inventory movement line within a product journal.Unique identifier of this journal line.
Item number (SKU) being adjusted or transferred.
Item description text.
Quantity for this adjustment or movement.
Unit of measure code for the
quantity.Quantity expressed in package units (e.g., cases, pallets).
Purchase UOM for this line when different from the base UOM.
Origin warehouse location code.
Destination warehouse location code.
Origin bin code.
Destination bin code.
Lot number for lot-tracked items.
Item variant code (e.g., size, color).
Quality classification code (e.g.,
"PASS", "HOLD", "REJECT").Movement type override for this specific line. When set, supersedes the header’s
movementType.ProductJournalSaveRequestDto
Request body for creating or updating a product journal, including its lines.Free-text description of the journal.
Default movement type for all lines in this save request.
Accounting date; if
null, the backend uses the current business date.External reference document number.
Transit location for inter-location transfer journals.
The inventory movement lines to create or replace for this journal.
ProductLocationOptionDto
A single warehouse location option used to populate the location picker on journal and movement screens.Warehouse location code (e.g.,
"MAIN", "ZONE-A"). The computed DisplayLabel falls back to LocationDescription ?? "Todos" when this is empty.Human-readable description for the location.
true for the location that should be pre-selected when the picker opens.ProductLocationListDto
Container returned by the location-list endpoint, wrapping available locations and the default selection.The location code that should be selected by default in the UI. Matches the
LocationCode of the entry with IsDefaultSelection = true.All locations available for selection. See ProductLocationOptionDto.
RFID Models
RFID DTOs drive tag resolution, device profile initialization, and operational policy enforcement for the integrated RFID reader.RfidTagResolveDto
Response returned when the handheld resolves a single EPC tag against the backend inventory.The Electronic Product Code read from the RFID tag. Unique tag identifier in hexadecimal format.
Type of inventory object the EPC represents (e.g.,
"ITEM", "PALLET", "CONTAINER").Tag registration status in the backend (e.g.,
"ACTIVE", "INACTIVE", "UNKNOWN").Backend item identifier linked to this EPC.
null if the tag is not associated with any item.Item number (SKU) resolved from this EPC.
Item description text for display in the scan-result overlay.
Quantity encoded on or associated with this RFID tag.
Warehouse location code where this tag’s item is registered.
Bin code associated with this tag.
true when the EPC was successfully matched to a known item in the backend.true when the RFID tag is active and eligible for warehouse transactions.Human-readable message from the backend, shown to the operator when
IsResolved is false or when the tag has a warning condition.RfidHandheldContextDto
Full RFID initialization context returned byGET /api/rfid/handheld/context. Drives all RFID capability decisions on the handheld, including fallback modes and device SDK initialization.
true when the backend successfully resolved the context for this device and module.The WMS module for which this context was requested (e.g.,
"RECEIVING", "SHIPMENT", "INQUIRY").The device identifier used to look up the device profile.
true when the device is registered and authorized in the tenant.true when a matching RFID device profile was found for this device.true when the device profile indicates RFID hardware support.true when the device profile indicates barcode scanning support.true when the tenant’s RFID policy enables RFID for the requested module.Computed authorization gate:
true only when the device is authorized, has a profile, supports RFID, and the module is RFID-enabled.true when operators may enter quantities manually instead of scanning.true when operators may use barcode scanning as a fallback to RFID.true when the module can proceed without any RFID scanning (manual or barcode only). Always true in the static Fallback() context.Enumerated hardware status code. Values:
"READY", "NO_RFID_PROFILE", "RFID_NOT_SUPPORTED", "RFID_DISABLED_BY_POLICY", "DEVICE_NOT_AUTHORIZED".Indicates how the device was identified (e.g.,
"REGISTERED_DEVICE", "DEFAULT_PROFILE", "NONE").Indicates the source of the effective policy (e.g.,
"MODULE_OVERRIDE", "TENANT_DEFAULT", "TENANT_DISABLED").The resolved operational mode for this module session (e.g.,
"RFID", "BARCODE", "MANUAL", "DISABLED").Optional human-readable message from the backend, shown as a warning or info banner on the handheld.
The effective RFID operation policy for the module. See RfidEffectivePolicyContextDto.
The effective device profile, containing SDK initialization parameters. See RfidEffectiveDeviceProfileContextDto.
RfidEffectiveDeviceProfileContextDto
The resolved RFID device profile containing all SDK initialization parameters for the handheld reader.true when a matching device profile was found in the tenant.true when this profile’s device supports RFID reading.true when this profile’s device supports barcode scanning.How the profile was matched:
"REGISTERED_DEVICE", "DEFAULT_PROFILE", or "NONE".Optional diagnostic message about the profile resolution.
Raw device identifier string from the registration.
Backend identifier of the registered handheld device record.
Backend identifier of the RFID device profile record.
Short code for the device profile (e.g.,
"ZEBRA-RFD90").Display name for the device profile.
Hardware vendor name (e.g.,
"Zebra", "Honeywell").Hardware model identifier.
OS or firmware platform string.
Physical connection type:
"UART" or "USB". Determines which SDK transport class is instantiated.Reader transport class selector:
"UART" or "USB".Read trigger mode:
"Manual" (single-press trigger) or "Continuous" (scan until released).Transmit power level in dBm passed to
setPower(). null means use the SDK default.Single-tag inventory session timeout in milliseconds.
Tag data to read per scan:
"EPC_ONLY", "EPC_TID", or "EPC_TID_USER".JSON blob of extended device capability flags.
JSON blob of additional device-specific settings.
true when this is the tenant’s default fallback profile (not device-specific).RfidEffectivePolicyContextDto
The effective RFID operation policy for the requested module. Controls fallback permissions, blocking rules, deduplication windows, and behavior for unknown or duplicate tags.true when the policy was successfully resolved for the module.true when RFID is globally enabled for the tenant.true when RFID is specifically enabled for the requested module.The WMS module this policy applies to.
Resolved operational mode:
"RFID", "BARCODE", "MANUAL", or "DISABLED".How the policy was resolved:
"MODULE_OVERRIDE", "TENANT_DEFAULT", or "TENANT_DISABLED".true when the policy permits operators to enter quantities manually.true when the policy permits barcode scanning as a fallback to RFID.true when the handheld must stop and alert the operator if an unregistered EPC is scanned.true when the handheld must block processing of tags marked inactive in the backend.true when the handheld must block processing when the scanned item does not match the expected item on the current document line.true when every RFID read must be recorded as an audit event in the backend.true when at least one RFID scan must be recorded before the operator can confirm/post a transaction.Window in seconds within which the same EPC is suppressed as a duplicate read.
0 means no deduplication is applied.Maximum number of distinct EPCs that may be collected in a single inventory session.
null means unlimited.Action when an unregistered EPC is scanned:
"ALLOW", "WARN", "BLOCK", or "REGISTER".Action when the same EPC is scanned again within the deduplication window:
"ALLOW", "WARN", or "BLOCK".Scope descriptor for the policy record (e.g.,
"MODULE", "TENANT").Optional informational message from the policy resolver.
SandboxResolvedItem
A lightweight resolved item record used in the RFID sandbox / simulation mode. Carries only the fields needed to render a scan result without a live backend connection.Item number (SKU) resolved from the simulated EPC read.
Item description text for display in the sandbox scan overlay.
Formatted RSSI signal-strength display string (e.g.,
"-65 dBm"). Defaults to "-" when signal data is unavailable.Scan mode indicator shown in the sandbox result (e.g.,
"RFID", "BARCODE", "MANUAL").Common Models
Shared utility DTOs used across multiple domains.PagedResponse<T>
Generic pagination wrapper returned by all list endpoints that support server-side paging.The current page number (1-based). Pass this value incremented by 1 to fetch the next page.
The number of records returned per page.
The total number of records in the full result set across all pages.
Total page count:
ceil(totalRecords / pageSize).The page’s data payload.
T is the domain-specific DTO for the endpoint being called.true when pageNumber > 1 and a previous page exists.true when pageNumber < totalPages and a next page exists.BinDto
Warehouse bin (storage location) record used in bin-selection pickers and bin-assignment flows.Unique backend identifier of the bin record.
Human-readable bin code displayed in pickers and on transaction lines (e.g.,
"A-01-01", "STAGE-01").Optional longer description of the bin location.
true when the bin is active and accepting inventory transactions.true when the bin is blocked — transactions referencing this bin will be rejected.true when this bin is the default location for its parent warehouse or zone.Bin classification code (e.g.,
"PICK", "BULK", "RECEIVE", "SHIP").true when the handheld may present this bin as a valid pick source.true when the handheld may suggest this bin as a valid put-away destination.CompanyResponse
Tenant company record returned by company-management endpoints.Unique identifier of the company. Used as the
CompanyId in all company-scoped API requests.Short alphanumeric company code (e.g.,
"ACME").Full legal or trading name of the company.
true when the company is active and users may log in to it.Company type classification (e.g.,
"MANUFACTURER", "DISTRIBUTOR", "RETAILER").ISO 4217 currency code for the company’s functional currency (e.g.,
"USD", "MXN", "EUR").IANA time zone identifier for the company (e.g.,
"America/Mexico_City", "UTC").true when the WMS module is activated for this tenant company.UTC timestamp when the company record was created.
CreateCompanyRequestDto
Request body posted to the company-creation endpoint when provisioning a new tenant.Short unique company code (e.g.,
"ACME"). Must be unique across all tenants.Trading or display name for the company.
ISO 4217 functional currency code (e.g.,
"USD").IANA time zone for date/time calculations (e.g.,
"America/New_York").Optional company type classification.
Legal registered name, if different from the trading name.
Tax identification number (e.g., RFC for Mexico, EIN for USA).
Primary street address line.
City name for the company’s registered address.
ISO 3166-1 alpha-2 country code (e.g.,
"MX", "US").TransferDto
TheTransferDto.cs file defines four DTOs that together model the complete inter-location transfer workflow.
TransferHeaderDto
The top-level transfer document header, returned by the transfer list and detail endpoints.External reference document number (e.g., an ERP transfer order number).
Unique event identifier for this transfer document in the event-sourcing model.
Key used to safely retry POST operations without creating duplicate transfers.
Distributed tracing correlation identifier for cross-service log correlation.
Transfer operation type (e.g.,
"TRANSFER", "RELOCATION").Transfer lifecycle status (e.g.,
"PENDIENTE", "ENVIADO", "RECIBIDO_PARCIAL", "COMPLETADO"). The computed StatusShortLabel and StatusBadgeColor derive from this value.Source warehouse location code. The computed
DisplayLocation falls back to "MAIN" when empty.Business partner (vendor/customer) code associated with this transfer.
Business partner display name.
UTC timestamp when the transfer was released for warehouse processing.
Individual product lines within this transfer document.
TransferLineDto
A single product line in a transfer document.External line number from the originating ERP transfer order.
Item number (SKU) being transferred on this line.
Item description text.
Quantity ordered for transfer. Used as the reference when
HeaderStatus is not "ENVIADO" or "RECIBIDO_PARCIAL".Quantity actually processed by the operator on the handheld.
Quantity confirmed as sent (dispatched). Used as the reference quantity when
HeaderStatus is "ENVIADO" or "RECIBIDO_PARCIAL".Quantity confirmed as received at the destination.
Unit of measure code for all quantities on this line.
Generic bin code associated with this line.
DisplaySourceBin falls back to this when SourceBinCode is null.Origin bin code where stock is picked from.
Destination bin code where stock is put away.
Injected by the ViewModel after the header loads so computed properties (
DisplayQty, Remaining) can adapt their reference quantity to the transfer state.PostTransferDto
Request body for posting a completed transfer back to the backend.Event identifier echoed from the originating transfer header.
Key to guarantee at-most-once semantics on the POST request.
Correlation identifier for distributed tracing.
External reference document number being posted.
Operation type. Defaults to
"TRANSFER".Target status after posting. Defaults to
"Posted".Source warehouse location code.
The confirmed transfer lines with actual quantities.
PostTransferLineDto
A single confirmed transfer line sent in aPostTransferDto request.
External line number identifying the corresponding line in the originating ERP document.
Item number (SKU) being transferred.
The originally expected quantity, echoed for reconciliation.
The quantity actually processed and confirmed by the operator.
Unit of measure for both quantity fields.
Origin bin code where stock was picked.
Destination bin code where stock was put away.
PickPageDto
Pick header record used on the pick-list screen. Links a pick document to its sales order and warehouse shipment.Unique identifier of the pick header.
System-generated pick document number displayed in the pick-list view.
Pick lifecycle status (e.g.,
"Open", "InProgress", "Completed").Display name of the user to whom this pick is assigned.
null if unassigned.Source sales order number. Links the pick document back to its originating sales order.
Warehouse shipment number associated with this pick. Links to the outbound
ShipmentHeaderDto.UTC timestamp when the pick document was created.
UTC timestamp when all lines were confirmed picked.
null if not yet complete.