> For the complete documentation index, see [llms.txt](https://tutorial.satubysmi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tutorial.satubysmi.com/readme.md). # Selamat Datang di SATU SATU adalah Partners Portal *multi-purpose* yang dirancang agar dapat memberikan Informasi, Solusi Bisnis Digital dan Bisnis Solusi use case untuk pertumbuhan bisnis Partner SMI.
## Solusi Digital Kami
B2B OnlineUntuk transaksi business-to-business (B2B) dengan dua metode pengiriman: ke gudang Partner atau langsung ke alamat Pembeli/End-User.Aktivasi Fitur
Dropship MarketplaceJual secara efisien melalui marketplace terkemuka tanpa perlu menyimpan stok, pemenuhan pesanan akan dikelola oleh tim gudang SMI.Basics
Dropship APIB2B atau B2C Partner E-Commerce yang mampu mengimplementasikan integrasi Direct API.FAQ
Digital KioskDigital Kiosk memadukan transaksi online dan offline, membuka peluang bisnis baru bagi mitra serta memperluas jangkauan portofolio produk Partner.
Autodesk & Microsoft LicenseSalah satu layanan yang terdapat dalam Web SATU yang memungkinkan partner melayani dan men-deliver digital license dan cloud service kepada pelanggan mereka.
Layanan API SATU

B2B atau B2C

Partner E-Commerce yang mampu mengimplementasikan integrasi Direct API.

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://tutorial.satubysmi.com/readme.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.