I don't know any specific naming conventions here - just use something “appropriate”, define a standard and stick to it :-)
If you are dealing with SOAP web services, they tend to be more focused on functions / methods - for example, your methods will be something like GetCustomeror UpdateCustomerOrderor the like. Try to find a consistent naming convention - do not use it Get....one time, Fetch....another time, and Load....next time. The same for preservation: do not use Save...., Store..or Put...- agree on one and stick to it.
If you are more in the style of REST WCF, then you are more concerned with resources , for example. you would be Customerand Orderand Inventoryas a resource to your URL-addresses, and then use the basic HTTP-verbs ( GET, PUT, POST, DELETE) to handle the basic CRUD operations.