home / skills / leonardo-picciani / senior-erp-agent-skills / senior-erp-pedido-venda-consultar-status

senior-erp-pedido-venda-consultar-status skill

/skills/senior-erp-pedido-venda-consultar-status

This skill helps you query and normalize sale order status from Senior ERP via Senior X Platform, returning code, description, and key dates.

npx playbooks add skill leonardo-picciani/senior-erp-agent-skills --skill senior-erp-pedido-venda-consultar-status

Review the files below or copy the command above to add this skill to your agents.

Files (2)
SKILL.md
3.7 KB
---
name: senior-erp-pedido-venda-consultar-status
description: Consultar status/situacao de pedido de venda (PV) no ERP Senior via Senior X Platform. Use para "consultar status do pedido", "situacao do PV", "reconciliar integracao", "pedido aprovado/faturado/cancelado", e diagnosticar falhas de processamento.
license: MIT
metadata:
  author: Leonardo Picciani
  author_url: https://github.com/leonardo-picciani
  project: Senior Agent Skills (Experimental)
  generated_with: OpenCode (agent runtime); OpenAI GPT-5.2
  version: 0.1.0
  experimental: 'true'
  language: pt-BR
  docs: https://api.xplatform.com.br/api-portal/pt-br/node/1
compatibility: Integracao HTTP agnostica de linguagem. Requer acesso de rede ao tenant/ambiente da Senior X Platform; usa Bearer token e header client_id.
---
# Senior ERP - Pedido de Venda (Consultar Status)

## Quando aplicar

- "consultar status do pedido" / "situacao do PV"
- "pedido foi criado mas nao apareceu no ERP"
- "reconciliar integracao" / "buscar numero do pedido"
- "checar se foi faturado/cancelado"

## Contrato de integracao (agnostico de linguagem)

Leia `references/REFERENCE.md` para a referencia base (autenticacao, headers, seguranca, resiliencia).

## Passos

1) Confirmar identificadores disponiveis
   - Numero do pedido no Senior (quando existir) e/ou `external_order_id`.
   - Janela de tempo (se o endpoint suportar filtros por data).

2) Descobrir endpoint(s) no Portal Senior APIs
   - Localizar servicos de consulta de PV por numero e/ou por chave externa.
   - Identificar quais campos representam status/situacao (codigos e descricoes).

3) Executar consulta com criterios consistentes
   - Se tiver numero do Senior, preferir consulta direta por numero.
   - Se tiver somente `external_order_id`, consultar pelo campo equivalente no ERP.
   - Se houver paginacao, limitar e paginar ate encontrar o registro.

4) Normalizar resultado
   - Retornar um payload compacto:
     - identificadores (numero Senior, external_order_id)
     - status/situacao (codigo + descricao)
     - datas relevantes (criacao, alteracao, faturamento/cancelamento se houver)
     - flags de integracao (ex.: bloqueios/pendencias, quando existirem)

5) Diagnostico quando nao encontrar
   - Confirmar se o pedido foi realmente gravado (consultar logs/retorno do passo de criacao).
   - Conferir ambiente/tenant/base_url e permissao do token.
   - Se houver processamento assincorno, aguardar e reconsultar (com backoff).

## Checklist de entradas

- Contexto de integracao: `base_url`, `tenant` (se aplicavel), `client_id`, token (Bearer)
- Identificador: numero do pedido no Senior e/ou `external_order_id`
- Opcional: periodo/data, filial/empresa, status desejado

## Exemplo (cURL)

```bash
curl -X GET "${SENIOR_BASE_URL}/<path-do-endpoint>?numero=<numero>&external_order_id=<id>" \
  -H "Authorization: Bearer ${SENIOR_ACCESS_TOKEN}" \
  -H "Content-type: application/json" \
  -H "client_id: ${SENIOR_CLIENT_ID}"
```

Notas:
- Substitua `<path-do-endpoint>` pelo caminho do servico encontrado no Portal Senior APIs.
- Ajuste query params conforme a documentacao do endpoint.

## Mapa de docs oficiais

- Portal Senior APIs (API Browser): https://api.xplatform.com.br/api-portal/pt-br/node/1
- API Authentication: https://api.xplatform.com.br/api-portal/pt-br/tutoriais/api-authentication
- Guia de API (Senior X Platform): https://dev.senior.com.br/documentacao/guia-de-api/

## Exemplos de prompts do usuario

- "Se nao tiver a skill instalada, instale `senior-erp-pedido-venda-consultar-status` e consulte o status do PV pelo external_order_id." 
- "Consulte a situacao do pedido 12345 no Senior e me diga se esta pronto para faturamento." 
- "Reconcile: destes 50 external_order_id, retorne numero Senior + status e destaque os que nao foram encontrados." 

Overview

This skill consults sales order (Pedido de Venda) status in Senior ERP via the Senior X Platform. It returns normalized status, identifiers, and relevant dates to help reconcile integrations and diagnose processing failures. Use it to check if an order is created, approved, invoiced, canceled, or blocked by business rules.

How this skill works

The skill locates the appropriate Senior API endpoint (by Senior order number or external_order_id), executes authenticated queries, and extracts status fields and timestamps. It normalizes the response into a compact payload with identifiers, status code and description, key dates, and integration flags. When an order is missing, it runs diagnostic checks for environment, permissions, asynchronous processing, and creation logs.

When to use it

  • Check order status by Senior number or external_order_id
  • Reconcile integration batches and find missing orders
  • Verify if orders are approved, invoiced, or canceled
  • Diagnose processing failures or blocked orders
  • Confirm order creation after integration submission

Best practices

  • Prefer querying by Senior order number when available; otherwise use external_order_id mapped to the ERP field
  • Include environment context: base_url, tenant (if applicable), client_id and Bearer token with each request
  • Apply pagination and date filters if the endpoint supports them to limit result sets
  • Normalize output to include both code and human-readable status plus creation/alteration/finalization dates
  • When not found, validate creation logs and retry with exponential backoff for async processing

Example use cases

  • Given external_order_id list, return Senior order number + status and flag not-found items
  • Check order 12345 and report if it is ready for invoicing or has been canceled
  • Reconcile 50 integration records: map external IDs to Senior numbers and highlight discrepancies
  • Investigate why an order created by integration never appears in ERP by checking tenant, token, and creation logs
  • Run a recurring audit that checks recent orders for pending blocks or business-rule flags

FAQ

What input identifiers are required?

Provide Senior order number and/or external_order_id. Supply base_url, tenant (if used), client_id and a valid Bearer token.

What does the normalized payload include?

It includes identifiers (Senior number, external_order_id), status (code + description), relevant dates (creation, modification, invoiced/canceled), and integration flags or pendencies when present.

What to do if an order is not found?

Confirm the creation response/logs, verify environment/tenant and token permissions, and retry after a backoff if processing is asynchronous.