Retail Clerk Role for Web Services in NetSuite

The Retail Clerk role for web services provides limited access for point-of-sale workflows, ensuring secure transaction processing without customization.

·2 min read·View Oracle Docs

Starting with the Retail Clerk role designated for web services, this role is specifically tailored for managing point-of-sale workflows in NetSuite. Unlike standard roles, the Retail Clerk (Web Services Only) role cannot be customized, providing an essential framework for web services transactions.

Key Functions of the Retail Clerk (Web Services Only)

The Retail Clerk (Web Services Only) role allows for specific operations within the NetSuite environment. Some primary functions include:

  • Access to Payment Audit Logs
  • Ability to create and manage billing information, including invoices and customer payments
  • Inquiry capabilities for bill of materials and charge rules
  • Access to employee public and employee records
  • Manage gift certificates and deposits
  • Interaction with REST and SOAP Web Services

Permissions and Limitations

One notable aspect of the Retail Clerk (Web Services Only) role is that its permissions are not adjustable. Users assigned this role will adhere to fixed access levels, which are strictly defined in relation to other standard roles. Here’s how the user counts are organized:

  • Assigning the Retail Clerk or Retail Clerk (Web Services Only) role alongside a full access role counts the user as one Retail Clerk.
  • If combined with any other non-Employee Center role, the user counts solely as a full-access user.
  • Assigning it along with an Employee Center role recognizes the user as both a Retail Clerk and Employee Center user.

For further information, see the permissions outlined in the Standard Roles Permissions Table.

Who This Affects

  • Administrators: Responsible for role assignment and management.
  • Developers: May need to understand the limitations of this role within API transactions.
  • Retail Staff: Users assigned this role for point-of-sale functionalities.

Key Takeaways

  • The Retail Clerk (Web Services Only) role is non-customizable and intended for secure web service transactions.
  • Limited access ensures transaction integrity without unnecessary complexity.
  • Role affects user-count metrics, impacting how resources are managed in NetSuite integrations.

Frequently Asked Questions (4)

What operations can the Retail Clerk (Web Services Only) role perform in NetSuite?
The Retail Clerk (Web Services Only) role can access payment audit logs, create and manage billing information, perform inquiries for bill of materials and charge rules, access employee records, and manage gift certificates and deposits.
Are the permissions for the Retail Clerk (Web Services Only) role in NetSuite customizable?
No, the permissions for the Retail Clerk (Web Services Only) role are fixed and cannot be customized.
How does the Retail Clerk (Web Services Only) role affect user-count metrics in NetSuite?
Assigning the Retail Clerk (Web Services Only) role alongside a full access role counts the user as one Retail Clerk. Combined with a non-Employee Center role, they count as a full-access user. With an Employee Center role, they are recognized as both a Retail Clerk and Employee Center user.
Does the Retail Clerk (Web Services Only) role for Web Services include both REST and SOAP interactions?
Yes, the Retail Clerk (Web Services Only) role includes interaction capabilities with REST and SOAP Web Services in NetSuite.
Source: Retail Clerk (Web Services Only) Oracle NetSuite Help Center. This article was generated from official Oracle documentation and enriched with additional context and best practices.

Was this article helpful?

More in Retail

View all Retail articles →