Search, compare current stock offers, and keep the evidence attached to the offer you choose.

1. Search by product or material. Select a category, origin evidence filter or documented U.S. ownership filter when needed.
2. Open the product to review its supplier, specifications, price, quantity and current stock offer. A product listing and a stock offer are separate records.
3. Check minimum quantity, available quantity and the offered currency. Request a quote when the listed offer does not cover the work.
4. Use the page's return links to keep your search and filters. A search result is not a certification or a legal country-of-origin determination.

Manufacturing location, business ownership and product-origin eligibility are different facts.

1. Choose the evidence filter that matches your procurement requirement. Strict U.S. origin and documented U.S. manufacturing do not mean the same thing.
2. Review the evidence associated with the selected current lot or offer. Evidence for another product or an older stock position may not apply.
3. Ask the supplier to clarify missing process, material or certification requirements before purchase. Do not infer a stronger claim from a badge or a listing's review status.
4. Use a private support conversation for account or evidence details that should not be posted publicly.

Give suppliers enough information to quote the exact work without disclosing unrelated company records.

1. Sign in to the correct business workspace. Describe the part or assembly, quantity, material, tolerances, finish and required delivery date.
2. Review the request before opening or sharing it. Identify which specific files and requirements may be disclosed to each supplier.
3. Compare quoted scope, price, lead time and exceptions. Ask for clarification when a quotation omits a required condition.
4. Accept only the exact terms you have reviewed. Save the resulting order reference and read the recorded confirmation before taking another commercial action.

Your personal identity, security factors and workspace membership have separate responsibilities.

1. Use Sign in for an existing account or Create an account when registering. Follow the verification requested by the signed-in flow.
2. Review available security-key and recovery options in Account security. Keep recovery material outside public forum posts and chat messages.
3. If a security-key or authenticator prompt is unclear, let the account holder complete it. Support does not need your password, one-time code, recovery code or private key.
4. Use Account recovery when you cannot sign in. An agent must not create another identity to bypass an account restriction.

Your account can participate in different business workspaces, each with its own records and roles.

1. Check the active workspace name before opening a private record or sending a request.
2. Save unfinished work before switching. The new workspace has its own inventory, accounting, files and operating data.
3. Use People and workspaces to review membership and available organization actions. A company role does not make you a platform support moderator.
4. If an action is disabled, review the visible reason or ask an authorized workspace administrator. Do not change a URL or automate clicks to bypass permission checks.

Public listings must be deliberately separated from private manufacturing information.

1. Open Products and purchases in your workspace and review the exact listing revision you intend to share.
2. Check the title, description, technical details and media. Remove private prices, drawings, customer information or machine details that are outside the approved disclosure.
3. Read publication, review and media availability states. A private saved draft is not a public listing, and an upload acknowledgement is not proof that a usable derivative was published.
4. Confirm the public disclosure presented by the workflow. If publication is unavailable or uncertain, inspect the saved record before retrying.

A recorded order, an open checkout page and a confirmed payment are different events.

1. Review the selected offer or accepted quotation, quantity, currency and exact commercial terms before placing an order.
2. Use only the checkout link supplied by the current order workflow. Read the provider and payment status shown for that order.
3. After returning from checkout, inspect the current order and payment record. Opening a provider page or seeing a temporary acknowledgement does not confirm settlement.
4. If the result is unclear, keep the existing order and request identity. Use Submitted actions and the available status check instead of placing another order or issuing another payment blindly.

Keep issue reporting tied to the correct order and preserve its evidence.

1. Open the relevant order and review its current fulfillment, receipt and payment status.
2. Record the specific problem, expected resolution and relevant shipment or acceptance facts. Share only the evidence required for that issue.
3. Use the order issue, return or refund task that is available to your account. A refund request is not a completed refund, and a platform case is not proof of a bank or card-network decision.
4. For a private support escalation, include the visible request reference and a short description. Do not post payment instruments, personal addresses or confidential evidence in the community forum.

Use the module that owns the record and review the effect of a command before submitting it.

1. Use Materials and BOMs for material requirements, Production planning for schedules, and Manufacturing execution for work in progress.
2. Check inventory and warehouse quantities against their recorded state. Posting a movement, receipt or production result can affect other workflows.
3. Use Accounting for accounts and financial entries. Confirm the business period, amount, currency and associated record before recording an entry.
4. Follow protected-action confirmations and keep the saved request reference. Guidance and support conversations do not replace deterministic authorization or physical safety controls.

A connection error can happen after a command was recorded. Repeating the action with a new identity can duplicate its effect.

1. Keep the current form and its reviewed terms. Do not close it, change the terms or submit another copy while the saved outcome is unresolved.
2. Use Find saved request, Inspect request, or the recovery action offered by that workflow. A safe retry reuses the retained request identity and exact terms.
3. Read the fresh recorded result before considering the action complete. If the workspace, role or account changed, return through the permitted recovery path.
4. If it remains unclear, start a private support conversation with the visible request reference, time and error message. Never include authentication material.

Agents use the same visible controls, account scope and permissions as the account holder.

1. Use page headings, named navigation regions, form labels, native option values and selected navigation to find the task. Confirm local loading and busy states before acting.
2. Keep marketplace filters and workspace selection in the existing URLs. Follow current record links rather than inventing identifiers.
3. State when a forum post or message is agent-assisted. This is a declaration attached to the connected account, not verification that the sender is an authenticated autonomous agent.
4. Ask the account holder when authorization or intent is unclear. Money, inventory, security, disclosure and machine actions retain their normal checks and confirmation steps.

Use the forum for a general question and live chat for account-specific clarification.

1. Search the guidance and published forum topics first. A good question names the task, expected result, actual result and steps already tried.
2. Sign in with the account that needs help. Forum posts and replies require an explicit confirmation that their contents may be published after moderation.
3. Use Live chat for private account or workspace details. AI troubleshooting is offered when available and requires explicit consent to share the conversation and authorized diagnostics with OpenAI. You can choose a human support specialist instead. Check the account and workspace before sending.
4. Review AI suggestions and their verification steps. If the result is still unclear, request a support specialist in the same conversation. Staff presence and response time are not guaranteed. A queued AI request is not a completed answer, and neither guidance nor a community reply overrides application permissions.