> ## Documentation Index > Fetch the complete documentation index at: https://docs.arcuserp.com/llms.txt > Use this file to discover all available pages before exploring further. # Undo a mistaken drop-ship (vendor-shipped) receipt > DROP-SHIP guided undo (2026-07-11, D9/F5). Reverses a mistaken "Mark shipped by vendor" event: reverses the drop-ship COGS + revenue/tax/shipping/discount recognition journal entries via linked reversal entries, voids the auto-created invoice and rebalances AR, rolls the sales order + purchase order quantities and statuses back, and removes the vendor shipment package (tracking preserved in the audit log). The already-sent customer shipment email cannot be unsent; the response surfaces `customer_email_already_sent` and a suggested follow-up (never auto-sent). Blocked when a vendor bill, a payment, or a return references the receipt, or the receipt is not the sole fulfillment event on a pure drop-ship order (see the eligibility preview). Requires `purchasing:write`. ## OpenAPI ````yaml /openapi.yaml post /purchase-receipts/{id}/undo-dropship openapi: 3.1.0 info: title: Arcus ERP Public API version: 1.0.0 description: > Arcus ERP public REST API. Designed for external integrations and data migration. **Authentication.** Bearer token (API key) via the `Authorization` header. Format: `Authorization: Bearer ark_live_ent__` (or `ark_test_*` for sandbox). API keys are issued per-entity in **Settings > Developers > API Keys**. **Entity scoping.** The entity is encoded in the API key prefix; routes are flat (e.g. `/v1/accounts`, `/v1/orders`, `/v1/products`). A small set of platform endpoints (migration, reconciliation, events, webhook endpoints, API keys) use the `/v1/entities/{entity_id}/...` form -- those are noted in their tags. **Key capabilities.** - Related-resource hydration via `?expand[]=` (see `x-arcus-expand` on each resource). - Cursor-based pagination (`starting_after` / `ending_before` / `limit`). - Idempotency via the `Idempotency-Key` header. - Webhook events for asynchronous notification. - Conditional requests / ETag for cache validation. servers: - url: https://api.arcuserp.com/v1 description: Arcus ERP API (accepts both live `ark_live_*` and test `ark_test_*` keys) - url: https://dev-api.arcuserp.com/v1 description: >- Dev sandbox API (test-only data, accepts `ark_test_*` keys against dev RDS) security: [] paths: /purchase-receipts/{id}/undo-dropship: parameters: - name: id in: path required: true schema: type: string format: uuid post: tags: - Purchasing summary: Undo a mistaken drop-ship (vendor-shipped) receipt description: > DROP-SHIP guided undo (2026-07-11, D9/F5). Reverses a mistaken "Mark shipped by vendor" event: reverses the drop-ship COGS + revenue/tax/shipping/discount recognition journal entries via linked reversal entries, voids the auto-created invoice and rebalances AR, rolls the sales order + purchase order quantities and statuses back, and removes the vendor shipment package (tracking preserved in the audit log). The already-sent customer shipment email cannot be unsent; the response surfaces `customer_email_already_sent` and a suggested follow-up (never auto-sent). Blocked when a vendor bill, a payment, or a return references the receipt, or the receipt is not the sole fulfillment event on a pure drop-ship order (see the eligibility preview). Requires `purchasing:write`. operationId: undoDropShipReceiptV1 requestBody: required: true content: application/json: schema: type: object required: - reason properties: reason: type: string description: >- Required; stamped on the reversal journal entries + audit log. responses: '200': description: Receipt undone (or idempotent replay when already reversed) content: application/json: schema: type: object properties: data: type: object properties: receipt_id: type: string format: uuid receipt_status: type: string reversed_journal_entries: type: array items: type: object voided_invoices: type: array items: type: string voided_packages: type: array items: type: object customer_email_already_sent: type: boolean suggested_followup: type: string nullable: true '401': $ref: '#/components/responses/Error' '403': $ref: '#/components/responses/Error' '404': $ref: '#/components/responses/Error' '422': $ref: '#/components/responses/Error' security: - ApiKeyAuth: [] components: responses: Error: description: Error response (400/401/403/404/409/422/429/500) content: application/json: schema: $ref: '#/components/schemas/ErrorEnvelope' schemas: ErrorEnvelope: type: object description: | Canonical error response envelope. All API errors use this shape. required: - error - code properties: error: type: string description: Machine-readable error key example: not_found code: type: string description: Machine-readable error code (often same as error) example: not_found type: type: string enum: - validation_error - permission_error - not_found - conflict - rate_limit - internal - expand_error - not_implemented example: not_found hint: type: string description: Human-readable one-sentence explanation (English) example: >- The requested order does not exist or does not belong to this entity. param: type: string description: The parameter that caused the error, if applicable example: expand[0] required: type: string description: The scope required (only on insufficient_scope errors) example: accounts:read request_id: type: string description: >- Unique request ID for support tracing (maps to CloudWatch log stream) example: req_abc123 securitySchemes: ApiKeyAuth: type: http scheme: bearer description: | API key issued per entity via Settings > Developers > API Keys. Each key carries scopes (e.g. orders:read, products:write). Bearer token format: Authorization: Bearer ark_live_ent__ Test keys use ark_test_ent__. Both are issued per entity via Settings > Developers > API Keys. ````